Fixes are available
PM11632; 6.1.0.31: transaction service partner log fills up leading to com.ibm.w
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 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
APAR status
Closed as program error.
Error description
After applying maintenance that includes PK92871 (included in fix packs 6.1.0.29 and 7.0.0.8), WebSphere MQ JMS XA transactional work will eventually result in the transaction service partner data becoming full. The following exception is observed: CWRLS0008E: Recovery log is being marked as failed. CWRLS0009E: Details of recovery log failure: com.ibm.ws.recoverylog.spi.LogFullException com.ibm.ws.recoverylog.spi.MultiScopeRecoveryLog.keypoint(MultiS copeRecoveryLog.java:1739) com.ibm.ws.recoverylog.spi.LogHandle.getWriteableLogRecord(LogHa ndle.java:1243) com.ibm.ws.recoverylog.spi.RecoverableUnitImpl.writeSections(Rec overableUnitImpl.java:677) com.ibm.ws.recoverylog.spi.RecoverableUnitImpl.forceSections(Rec overableUnitImpl.java:1054) com.ibm.ws.recoverylog.spi.RecoverableUnitImpl.forceSections(Rec overableUnitImpl.java:993) com.ibm.ws.Transaction.JTA.PartnerLogData.logData(PartnerLogData .java:216) com.ibm.ws.Transaction.JTA.PartnerLogData.logRecoveryEntry(Partn erLogData.java:159) com.ibm.ws.Transaction.JTA.RegisteredResources.enlistResource(Re gisteredResources.java:627) com.ibm.ws.Transaction.JTA.TransactionImpl.enlistResource(Transa ctionImpl.java:3296) com.ibm.ws.Transaction.JTA.TranManagerSet.enlist(TranManagerSet. java:406) com.ibm.ejs.j2c.XATransactionWrapper.enlist(XATransactionWrapper .java:699) com.ibm.ejs.j2c.ConnectionEventListener.interactionPending(Conne ctionEventListener.java:940) com.ibm.ejs.jms.JMSManagedSession.interactionPending(JMSManagedS ession.java:1071) com.ibm.ejs.jms.JMSManagedSession.enlist(JMSManagedSession.java: 910) The following exception may also be seen: WTRN0000E: An internal error occurred in method logData in class com.ibm.ws.Transaction.JTA.PartnerLogData; the exception stack trace follows: com.ibm.ws.recoverylog.spi.InternalLogException com.ibm.ws.recoverylog.spi.MultiScopeRecoveryLog.createRecoverab leUnit(MultiScopeRecoveryLog.java:1265) com.ibm.ws.recoverylog.spi.RecoveryLogImpl.createRecoverableUnit (RecoveryLogImpl.java:168) com.ibm.ws.Transaction.JTA.PartnerLogData.logData(PartnerLogData .java:203) com.ibm.ws.Transaction.JTA.TransactionImpl.enlistResource(Transa ctionImpl.java:3296) com.ibm.ws.Transaction.JTA.TranManagerSet.enlist(TranManagerSet. java:406) com.ibm.ejs.j2c.XATransactionWrapper.enlist(XATransactionWrapper .java:699) com.ibm.ejs.j2c.ConnectionEventListener.interactionPending(Conne ctionEventListener.java:940) com.ibm.ejs.jms.JMSManagedSession.interactionPending(JMSManagedS ession.java:1071) com.ibm.ejs.jms.JMSManagedSession.enlist(JMSManagedSession.java: 910)
Local fix
Increasing size of partnerlog might delay the occurence of the problem but not eliminate it.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server 6.1 and 7.0 with WebSphere MQ JMS * **************************************************************** * PROBLEM DESCRIPTION: After applying PK92871, XA MQ JMS work * * eventually causes the transaction * * service partner log to become full. * **************************************************************** * RECOMMENDATION: The speed at which the partner log becomes * * full varies according to the workload and * * Connection pool configuration. A new * * entry is added to the partner log * * every time a Connection is created. New * * Connections are created when there are no * * free Connections in the Connection Pool, * * and the number of Connections is less than * * the maximum. * * * * Connections are destroyed and removed * * from the pool via the unused timeout or * * aged timeout settings. Unused connections * * are usually destroyed during periods of * * low workload volumes whereas aged timeout * * destroys Connections on a regular basis. * * * * In the unused timeout case, the log could * * become full after a period of weeks or * * even months. In the aged timeout the log * * could become full after a few days. * **************************************************************** PK92871 changed a String identifier. This change broke logic used to determine if two XAResources are in fact equal (for the purposes of recording the XAResource as a partner in the partner log). As a result the transaction service could not determine that it had already recorded the partner details in the log and so for every Connection created, a new entry was made.
Problem conclusion
This APAR fixes the String identifier which allows the existing logic to correctly determine equality. The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.33 and 7.0.0.11. 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
PM11632
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-04-06
Closed date
2010-04-13
Last modified date
2010-05-13
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
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
Document Information
Modified date:
24 October 2021