Fixes are available
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
When com.ibm.websphere.threadmonitor.dump.java is set to true and if com.ibm.websphere.threadmonitor.dump.java.track is NOT set then by default a java thread dump is created continuously at the default hung thread detection time interval (default 3 mins). So basically it will continuously produce java thread dumps every minute while the thread remains hung. In customer situation the hung thread never recovers and as a result a java thread dump is produced every 3 minutes and fills up gigabytes of storage.
Local fix
You can set com.ibm.websphere.threadmonitor.dump.java to 1
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: The hung thread detection system * * repeatedly dumps javacores for the * * same hung thread * **************************************************************** * RECOMMENDATION: * **************************************************************** The WebSphere Application Server thread monitor allows users to track hung threads by periodically dumping a javacore as long as the thread is detected as hung, using the com.ibm.websphere.threadmonitor.dump.java.track property. If this property is unset, the default value is set to be identical to the value of com.ibm.websphere.threadmonitor.dump.java. If the property is set to "true", the thread monitor sets those properties to the maximum integer value, so a thread hung for a long period of time would cause javacores to be thrown basically indefinitely. Users who had used this property on previous editions of WebSphere Application Server would have been likely to use the "true" value, as the property utilized boolean values in its original incarnation, but since the "track" property did not exist, they would have only had one javacore thrown per thread.
Problem conclusion
The default value of the "track" property was modified so that if left unset, only one javacore would be thrown for a single hung thread. The fix for this APAR is currently targeted for inclusion in fix packs 8.5.5.12 and 9.0.0.3. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
As a workaround, users can set the system property com.ibm.websphere.threadmonitor.dump.java.track to "1".
Comments
APAR Information
APAR number
PI65836
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-07-13
Closed date
2016-11-22
Last modified date
2016-11-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
04 May 2022