62 lines
2.8 KiB
HTML
62 lines
2.8 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Configure the hang detection policy</title>
|
||
|
|
</head>
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
<h4><a name="trbconfighangdet"></a>Configure the hang detection policy</h4>
|
||
|
|
|
||
|
|
<p>The thread hang detection option is enabled by default. Perform the following steps
|
||
|
|
to adjust the hang detection policy values, or to disable hang detection completely:</p>
|
||
|
|
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li>From the administrative console, click <strong>Servers</strong> --> <strong>Application Servers</strong> --> <em>server_name</em>.</li>
|
||
|
|
<li>Under Additional Properties, click <strong>Custom Properties</strong>.</li>
|
||
|
|
<li>Click <strong>New</strong>.</li>
|
||
|
|
<li>Add the following properties:
|
||
|
|
<pre><strong>Name:</strong> com.ibm.websphere.threadmonitor.interval
|
||
|
|
<strong>Value:</strong> The frequency (in seconds) at which managed threads in the selected
|
||
|
|
application server will be interrogated.
|
||
|
|
<strong>Default:</strong> 180 seconds (three minutes).
|
||
|
|
|
||
|
|
<strong>Name:</strong> com.ibm.websphere.threadmonitor.threshold
|
||
|
|
<strong>Value:</strong> 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.
|
||
|
|
<strong>Default:</strong> The default value is 600 seconds (ten minutes).
|
||
|
|
|
||
|
|
<strong>Name:</strong>com.ibm.websphere.threadmonitor.false.alarm.threshold
|
||
|
|
<strong>Value:</strong> 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 threshold 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.
|
||
|
|
<strong>Default:</strong> 100
|
||
|
|
</pre>
|
||
|
|
|
||
|
|
<p>See <a href="trbhangdet.htm#falsealarms">Detect hung threads in J2EE applications</a> for more information on false alarms.</p>
|
||
|
|
|
||
|
|
<p>To disable the hang detection option, set the <strong>com.ibm.websphere.threadmonitor.interval</strong> property
|
||
|
|
to less than or equal to zero.</p>
|
||
|
|
|
||
|
|
</li>
|
||
|
|
<li>Click <strong>Apply</strong>.</li>
|
||
|
|
<li>Click <strong>OK</strong>.</li>
|
||
|
|
<li>Save the changes and make sure a file synchronization is performed
|
||
|
|
before restarting the servers.</li>
|
||
|
|
<li>Restart the application server for the changes to take effect.
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|