Example: Adjust the thread monitor to affect server hang detection
The hang detection policy affects how the appserver responds to a thread not being processed correctly.
You can adjust the thread monitor settings using wsadmin. These changes take effect immediately, but do not persist to the server configuration, and are lost when the server is restarted.
# 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
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 Java EE applications
Related tasks
Set the hang detection policy