WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Configuring the hang detection policy

Why and when to perform this task

The thread hang detection option is enabled by default. To adjust the hang detection policy values, or to disable hang detection completely:

Steps for this task

  1. From the administrative console, click Servers > Application Servers > server_name
  2. Under Server Infrastructure, click Administration > Custom Properties
  3. Click New.
  4. Add the following properties:
    Name: com.ibm.websphere.threadmonitor.interval
    Value:  The frequency (in seconds) at which managed threads in the selected 
            application server will be interrogated.
    Default: 180 seconds (three minutes). 
    
    Name: com.ibm.websphere.threadmonitor.threshold
    Value:   The length of time (in seconds) in which a thread can be active 
             before it is considered hung.  Any thread that is detected as 
             active for longer than this length of time is reported as hung.
    Default: The default value is 600 seconds (ten minutes).
    
    Name:com.ibm.websphere.threadmonitor.false.alarm.threshold 
    Value: The number of times (T) that false alarms can occur 
           before automatically increasing the threshold. It is possible that a 
           thread that is reported as hung eventually completes its work, 
           resulting in a false alarm.  A large number of these events indicates 
           that the threshhold value is too small. The hang detection facility can 
           automatically respond to this situation: For every T false alarms, the 
           threshold T is increased by a factor of 1.5. Set the value to 
           zero (or less) to disable the automatic adjustment. 
    Default: 100
    
    To disable the hang detection option, set the com.ibm.websphere.threadmonitor.interval property to less than or equal to zero.
  5. Click Apply.
  6. Click OK.
  7. Save the changes and make sure a file synchronization is performed before restarting the servers.
  8. Restart the Application Server for the changes to take effect.



Related concepts
Detecting hung threads in J2EE applications

Related reference
Adjusting the hang detection policy of a running server

Task topic    

Terms of Use | Feedback

Last updated: Mar 17, 2005 4:28:29 AM CST
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/ttrb_confighangdet.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)