Reconnect RCP connection or close RCP connection and Reconnect it and check.
Also, after timeout Job got killed automatically.
Thank you for the reply.
I made this phenomenon reproduce.
However, on the server console, the status of the job remains with running and
the job remains in the "Tasks in Progress" on th console.
Is there how to cancel this job?
have you restarted the appserver since you reconnected the db network connection?
are there any active work item threads on your appserver dedicated to running the job ?
I confirmed after restarting the application server, a job will be cleared.
However, we would like to clear Job without restarting an application server.
Because, we have more than one user who operates BladeLogic Server Automation.
If network failure occurs between appserver and DB server, is it necessary to restart the application server ?
It depends what happens.
Next time this happens, I would get a thread dump from the appserver running the job and we can investigate the state of the WIT that’s running the job and determine why it’s stuck.
Is the network dropping a frequent occurrence in your environment ?
Are you sure this thread dump is from the appserver w/ the stuck job? I don’t see any of the WIT running any jobs. what kind of job was supposedly running here?
Yes, I got thread dump immediately after this phenomenon occurred.
Job type is NSH script job and the name is testnshx.
After that, if canceling the job, the job remains running.
I upload the thread dump and screen at that time too.
- However, the Job is not cancel.
Thread infotxt.txt 129.9 K