PM11632: TRANSACTION SERVICE PARTNER LOG FILLS UP LEADING TO COM.IBM.WS.RECOVERYLOG.SPI.LOGFULLEXCEPTION AFTER PK92871

Fixes are available

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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM11632: TRANSACTION SERVICE PARTNER LOG FILLS UP LEADING TO COM.IBM.WS.RECOVERYLOG.SPI.LOGFULLEXCEPTION AFTER PK92871

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?