Killing WAS Managed Threads?

[EoinWoods]

WAS 6 introduces the useful feature of reporting threads that it thinks are hung. However, it's not really clear how you're meant to manage the situation if this happens.

Is there some way of killing a hung thread via WAS? After all, these are managed threads.

Thanks for any ideas.

Eoin.
--
Eoin Woods, UBS Investment Bank, London

[Andy Wilkinson]

Eoin,

There is no mechanism in WAS to allow you to kill a thread that has been
identified as hung. The intention of the reporting of hung threads is to
aid with problem identification and determination, e.g. if a thread is
identified as hung it may be appropriate to take a thread dump of the
server to identify in what method the thread has hung.

Regards,
Andy Wilkinson
IBM

[EoinWoods]

OK, thanks for the information.

[Ben_]

> Is there some way of killing a hung thread via WAS? After all, these are
managed threads.

No. Stopping threads in Java cannot be done externally without the thread
collaborates.
There is pretty much literature on this topic in multi-threading tutorials
and books.
Basically, what can be done is send the thread a signal to *ask* it to stop.
But if no code is foreseen to abide to the signal, the thread cannot be
stopped externally.