While using engine command“KillProcessInstance“on the process where it involves TCP socket connection especially third party socket connection, it is not able to kill the process. Instead it marks the process in Dead status. Why?
Article ID: KB0091744
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Resolution:
When the thread is waiting on socket read, Engine Kill command seems to have deleted the job but the thread is still waiting for the socket read to complete. Until that time the job is marked as DEAD. The only way to get rid of the DEAD jobs in this case is to have minimum SOTimeout(Socket time out) so that the dead jobs will disappear and threads will be alive to process the further jobs coming in.
Hawk thread will not have any control over the objects in the thread which is waiting on socket read. We would not have any handle of the socket so that the socket can be closed. Hence minimum Socket timeout has to be specified in this scenario.
KEYWORDS:ENGINE COMMAND,KILL, SOCKET
Issue/Introduction
While using engine command“KillProcessInstance“on the process where it involves TCP socket connection especially third party socket connection, it is not able to kill the process. Instead it marks the process in Dead status. Why?
Feedback
Yes
No
Powered by
