Example: Adjusting the thread monitor to affect server hang detection

 

The hang detection policy affects how the appserver responds to a thread that is not being processed correctly. You can adjust the thread monitor settings by using the wsadmin scripting interface. These changes take effect immediately, but do not persist to the server configuration, and are lost when the server is restarted. The following script provides an example of how to adjust the properties for the thread monitor using the wsadmin tool:

# Read in the interval, threshold, false alarm from the command line set interval [lindex $argv 0] set threshold [lindex $argv 1] set adjustment [lindex $argv 2]

# Get the object name of the server you want to change the values on set server [$AdminControl completeObjectName "type=Server,*"]

# Read in the interval and print to the console set i [$AdminControl getAttribute $server threadMonitorInterval]

# Read in the threshold and print to the console set t [$AdminControl getAttribute $server threadMonitorThreshold]

# Read in the false alarm adjustment threshold and print to the console set a [$AdminControl getAttribute $server threadMonitorAdjustmentThreshold]

# Set the new values using the command line parameters
$AdminControl setAttribute $server threadMonitorInterval  ${interval}

$AdminControl setAttribute $server threadMonitorThreshold ${threshold}

$AdminControl setAttribute $server threadMonitorAdjustmentThreshold ${adjustment}

---

 

Related concepts

Hung threads in J2EE applications

 

Related tasks

Configure the hang detection policy

 

Reference topic