Fixes are available
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
Heapdump data will identify a leak suspect similar to the following... 1,056,863,400 (24.76%) [439,736] 34,293 array of java/lang/Comparable 0x7f2d39a38 3,183,304 (0.07%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7fc8dd390 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7b36b8f88 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x79b130ad0 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7a4b4cd70 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x79c2a0190 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7a5b11d20 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7eed229a0 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7f84926d0 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7b1582280 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7a3606ba0 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7b39387e8 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7b22267f0 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7acebe4c0 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7a26feac0 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7a860d2d0 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7f4583608 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7f54efcc8 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7a20b5cd8 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x795f48240 38,464 (0%) [72] 2 com/ibm/ws/asynchbeans/am/_Alarm 0x7a78ce418 There are 34,273 more children
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 scheduler alarms * **************************************************************** * PROBLEM DESCRIPTION: Scheduler alarm object not removed * * from the alarm queue when alarm * * worker threads are blocked * **************************************************************** * RECOMMENDATION: * **************************************************************** When the scheduler workmanager threads are blocked due to application specific reasons where the TaskHandlerBean process() method does not return since they may be waiting for the work it started, there is a possibility for the scheduler alarm objects to stay in the alarm queue forerver. When there are large number of repeating scheduler tasks, for every poll, cycle alarms will be scheduled and added to the alarm queue. And if these alarms are not fired due to a scarcity of WorkManager threads within that poll cycle, then all of these pending alarms will get cancelled in the next poll cycle and will be created again. However the cancelled alarms are not getting removed from the AlarmManager's alarm queue data structure and hence can get get piled up in the heap which could lead to an OutOfMemory condition.
Problem conclusion
The WebSphere asynchbeans component has been corrected. This APAR will prevent the reported OutOfMemory due to the accumulation of _Alarm objects and is enabled with a JVM custom property named: com.ibm.ws.asynchbeans.am.clearAlarmQueue To set the JVM custom property: In the administrative console, go to Servers -> Application Servers -> server name -> Process Definition -> Java Virtual machine. Select Custom Properties and click New. Enter com.ibm.ws.asynchbeans.am.clearAlarmQueue as the name and true as the value. Save the changes and restart the server. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.10 and 8.5.5.4. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI20194
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-06-17
Closed date
2014-09-26
Last modified date
2014-09-26
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
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022