Fixes are available
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
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
Deadlock occurring when the log is rotated often.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * * V8.5.5 and V9.0. * **************************************************************** * PROBLEM DESCRIPTION: Deadlock occurred when the WebSphere * * Application Server logs are frequently * * rotated, based on file size (>= 1 MB). * **************************************************************** * RECOMMENDATION: * **************************************************************** When logs are rotated often, based on file size, a deadlock occurs, when there is a circular dependency between threads that contend for the SystemOutStream.logMessage() and synchronized Tr.dispatchIntervalEvents() methods. There is a deadlock between the following threads: Blocked on: com/ibm/ejs/ras/Tr@0x00000006000A1C90 Owned by: "WebContainer : 21" (J9VMThread:0x0000000005C4D200, java/lang/Thread:0x00000006506DBF70) Heap bytes allocated since last GC cycle=0 (0x0) Java callstack: at com/ibm/ejs/ras/Tr.event(Tr.java:776(Compiled Code)) at com/ibm/ejs/ras/TraceNLS.worker(TraceNLS.java:724(Compiled Code)) at com/ibm/ejs/ras/TraceNLS.getStringFromBundle(TraceNLS.java:502(C ompiled Code)) and Blocked on: com/ibm/ejs/ras/SystemOutStream@0x00000006011DB7B8 Owned by: "Dispatcher-Thread-56" (J9VMThread:0x0000000001B5E800, java/lang/Thread:0x000000060142E7F8) Heap bytes allocated since last GC cycle=0 (0x0) Java callstack: at com/ibm/ejs/ras/SystemOutStream.logMessage(SystemOutStream.java: 330(Compiled Code)) (entered lock: com/ibm/ejs/ras/SystemOutStream@0x00000006011DB7B8, entry count: 1) at com/ibm/ejs/ras/SystemOutStream.processEvent(SystemOutStream.jav a:319(Compiled Code)) at com/ibm/ws/logging/WsHandlerWrapper.publish(WsHandlerWrapper.jav a:43(Compiled Code)) at java/util/logging/Logger.log(Logger.java:628(Compiled Code)
Problem conclusion
The deadlock issue was resolved by reducing the amount of synchronization from the Tr.dispatchInternalEvents() method, which would reduce the possibility of needing to lock the Tr class, when logs are rotated often. The fix for this APAR is currently targeted for inclusion in fix packs 8.5.5.11 and 9.0.0.2. 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
PI66579
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-07-27
Closed date
2016-09-20
Last modified date
2016-09-20
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022