PQ91814: HangDetection threshold adjustment algorithm fails to adjust when initial threshold value is set to 1. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Per the online documentation, if you set the false alarm threshold to a certain value (1 in this case) and the false alarm threshold value has been reached, the detect hang policy should adjust the thread.monitor threshold by a value of (threadmonitor.threshold value) x 1.5 = new threadmonitor.threshold value. I am finding this to be the case when my initial threshold value is greater than 1, however, if the value is equal to 1, the threshold value never gets increased to a value greater than 1 when it is reset. Example: ThreadMonitor W WSVR0607W: Too many thread hangs have been falsely reported. The hang threshold is now being set to 1 seconds The above example shows that the hang threshold is being set to 1 even though it was already set to 1 initially. 1 x 1.5 = 1Local fix Problem summary **************************************************************** * USERS AFFECTED: Potentially all users are affected * **************************************************************** * PROBLEM DESCRIPTION: When using the HangDetection * * capabilites of the appserver with * * extremely low time values (1 second), * * the threshold will not adjust up as * * documented. * **************************************************************** * RECOMMENDATION: * **************************************************************** Due to the way integer math works, when calculating the new HangDetection threashold, truncation results in an inability to adjust the threashold upwards when the value is initially set to 1 second (this would be a very unusual setting and pratically not be used).Problem conclusion The HangDetection threshold adjustment algortithm now incorporates a rounding algorithm that allows the adjustment calculation to round up the answer, thereby preventing the adjusted threashold from being effectively stuck at 1 (in effect 1 + .5 = 2). This is essentially protecting this algorithm under all boundry conditions.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 10W
Software edition:
Reference #: PQ91814
IBM Group: Software Group
Modified date: Aug 10, 2004
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.