How to kill a single Java thread ID?

[Former Member]

All

How to kill a single Java thread ID without recycling the entire Java process, via SMICM or jcmon?

Kindly let me know if there any method followed for the same.

Regards

Jim

[Former Member · Accepted solution]

Hi,

Login to http://<hostname>:50000/nwa/start-stop.

2.Goto Java EE Services.

3.Search for service <thread>

4.Restart this service.

5.Go back to MMC and refresh . All red threads will become green.

*If NWA is not accessible , then the service has to be restarted from telnet .*

1.login through putty or if it is wondows go to cmd

2.Give command telnet localhost 50008

3.login via j2ee_admin & master pwd

4.STOPSERVICE <Thread>

5.STARTSERVICE <Thread>

6.Refresh in MMC

[Former Member · Accepted solution]

Hi

Thanks for your response. However I have few more queries on this:

1) How to identify the service, associated for java threads that are shown under SMICM ?

2) We are not able to associate or find the threads in NWA. How to find them?

Regards

James

[Former Member · Accepted solution]

Hello,

I have the same problem. I have a NW'04 Java Stack in which one thread has been running for several days and I would like to kill it.

I have telnetted but I cannt find the correct syntax. The information I have is: "SAPEngine_Application_Thread[impl:3]_15" but stopservice SAPEngine_Application_Thread[impl:3]_15

stopservice SAPEngine_Application_Thread_15

do not work. I cannot seem to figure out what to put in and in the meantime CPU is going up and GC is also still extremely frequent.

[Former Member · Accepted solution]

Hello,

I have the same problem. I have a NW'04 Java Stack in which one thread has been running for several days and I would like to kill it.

I have telnetted but I cannt find the correct syntax. The information I have is: "SAPEngine_Application_Thread[impl:3]_15" but stopservice SAPEngine_Application_Thread[impl:3]_15

stopservice SAPEngine_Application_Thread_15

do not work. I cannot seem to figure out what to put in and in the meantime CPU is going up and GC is also still extremely frequent.