Kill Thread Within Java.exe Process

[John A. Bailo]

I am monitoring a java application (running as a Windows service) from
a third party.

psinfo shows me all threads, and I noticed there were two that have
been running over 9 hours. It was about 9 hours ago that CPU
utilization on my Windows 2000 Server went up to 50%.

I know I use pskill to stop the entire java.exe -- but is there an
external command or program I can write to kill an individual thread
inside a java.exe ?

 

[Daniel Pitts]

I am monitoring a java application (running as a Windows service) from
a third party.

psinfo shows me all threads, and I noticed there were two that have
been running over 9 hours. It was about 9 hours ago that CPU
utilization on my Windows 2000 Server went up to 50%.

I know I use pskill to stop the entire java.exe -- but is there an
external command or program I can write to kill an individual thread
inside a java.exe ?

No. You'll have stop the entire Java proces and start it again.

 

[Eric Sosman]

I am monitoring a java application (running as a Windows service) from
a third party.

psinfo shows me all threads, and I noticed there were two that have
been running over 9 hours. It was about 9 hours ago that CPU
utilization on my Windows 2000 Server went up to 50%.

I know I use pskill to stop the entire java.exe -- but is there an
external command or program I can write to kill an individual thread
inside a java.exe ?

Not unless you've arranged a way for the threads to stop
on (or shortly after) some external stimulus.

See the Javadoc for Thread#stop() to understand why this
cannot even be done safely from inside the Java program, much
less from the outside.

 

[Mike Schilling]

Not unless you've arranged a way for the threads to stop
on (or shortly after) some external stimulus.

One way of doing this to to run the JVM as debuggable. That lets you attach
a debugger later, examine the threads, and kill whichever ones you like.

See the Javadoc for Thread#stop() to understand why this
cannot even be done safely from inside the Java program, much
less from the outside.

That's true, of course.