Fixes are available
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
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
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
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
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.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
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
While accessing the transaction service logs a deadlock occurs in the control region and the servant region times out. The callstacks of the deadlocked threads in the control region will look like: CR thread A: java/lang/Object.wait(Object.java:167) com/ibm/ws/recoverylog/spi/Lock.getSharedLock(Lock.java:193) com/ibm/ws/recoverylog/spi/LogCursorImpl.<init>(LogCursorImpl.ja va:281) com/ibm/ws/recoverylog/spi/LogCursorImpl.<init>(LogCursorImpl.ja va:199) com/ibm/ws/recoverylog/spi/MultiScopeRecoveryLog.recoverableUnit s(MultiScopeRecoveryLog.java:1526) com/ibm/ws/recoverylog/spi/RecoveryLogImpl.recoverableUnits(Reco veryLogImpl.java:206) com/ibm/ws390/recoverylog/spi/ControllerRequestProcessor.driveRe coveryLogMethod(ControllerRequestProcessor.java:260) com/ibm/ws390/recoverylog/spi/ControllerRequestProcessor.process (ControllerRequestProcessor.java:135) CR thread B: com/ibm/ws/recoverylog/spi/MultiScopeRecoveryLog.payloadWritten( MultiScopeRecoveryLog.java:2038) com/ibm/ws/recoverylog/spi/RecoverableUnitImpl.payloadWritten(Re coverableUnitImpl.java:1603) com/ibm/ws/recoverylog/spi/RecoverableUnitSectionImpl.payloadWri tten(RecoverableUnitSectionImpl.java:1111) com/ibm/ws/recoverylog/spi/DataItem.write(DataItem.java:241) com/ibm/ws/recoverylog/spi/RecoverableUnitSectionImpl.format(Rec overableUnitSectionImpl.java:718) com/ibm/ws/recoverylog/spi/RecoverableUnitImpl.writeSections(Rec overableUnitImpl.java:700) com/ibm/ws/recoverylog/spi/MultiScopeRecoveryLog.keypoint(MultiS copeRecoveryLog.java:1767) ... This issue may present itself as a failure to start a message listener port.
Local fix
Restart application server controller.
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V7.0, V8.0 and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: A deadlock occurs in the control * * region while accessing the transaction * * service logs causing a timeout in the * * servant region. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABBA deadlock occurred in the control region between a thread that was obtaining the list of recoverable units from the transaction service partner log and a thread that was keypointing the same log.
Problem conclusion
The locking was modified so that the ABBA deadlock can no longer occur. APAR PI43413 is currently targeted for inclusion in Fix Packs 7.0.0.41, 8.0.0.12 and 8.5.5.9 of WebSphere Application Server. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PI43413
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-06-19
Closed date
2015-10-08
Last modified date
2016-05-11
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI50202
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UI36529
UP16/04/09 P F604
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
28 April 2022