How can the administrator determine that the hung threads are a false alarm?

An application deployed to a multi-node cluster is reported to have slowness and hung threads. A system administrator is asked to review the logs on each node and identify if the hung threads are a false alarm.

How can the administrator determine that the hung threads are a false alarm?

Analyze the:
A . ffdc logs
B . SystemErr.log
C . SystemOut.log
D . native_stderr.log

View Answer

Answer: C

Explanation:

Problem (Abstract)

The SystemOut.log contains a WSVR0605W message, also called a hung thread message. A javacore, or thread dump on Solaris and HP-UX, is needed in order to determine how to resolve the potentially hung threads.

Cause

WebSphere Application Server attempts to report potentially hung threads using the hung thread detector. Depending on how the hung thread detector policy is configured, a thread running for a certain interval (default 10 minutes) might be reported as hung and a WSVR0605W message is printed in the SystemOut.log file:

WSVR0605W: Thread <threadname> has been active for <time> and may be hung. There are <totalthreads> in total in the server that may be hung.

References: https://www-01.ibm.com/support/docview.wss?uid=swg21448581