PM06658: TRIGGER CREATION OF RRS NATIVE LTC FOR UNSHARABLE CONN IN BMT

Fixes are available

APAR status

Closed as program error.

Error description

In a V7 optimization, Resource Recovery Services (RRS) Native
LTCs should be created whenever a connection is established to
an RRS-capable resource within a WebSphere Application Server
LTC.  When the LTC is started, the TM will create an RRS
NativeLTC upon invoking a J2C RRSLocalTransactionWrapper
instance to addSync(), which registers the wrapper (sync
object) with the TM.  J2C does not register the
RRSLocalTransactionWrapper when the connection is unsharable
and the transaction is application-managed (BMT), which causes
the TM to not create the RRS Native LTC.  The wrapper is not
registered to ensure the TM does not affect connection
management when the transaction is completed.

We shall resovle this oversight by registering an
RRSNoTransactionWrapper to the TM in this scenario.  The
wrapper provides no synchronization behaviors.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  on z/OS deploying applications that         *
*                  perform local transactions involving        *
*                  RRS-capable resources.                      *
****************************************************************
* PROBLEM DESCRIPTION: A native RRS local transaction          *
*                      context is not created when             *
*                      connecting to an RRS-capable resource   *
*                      within an Application Server            *
*                      local transaction.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a connection is established to an RRS-capable resource
within a WebSphere Application Server local transaction,
native RRS local transaction context (LTC) is not created.
This causes any existing RRS transactional context to not
suspend when work executes under the WebSphere Application
Server local transaction.  When the local transaction is
cleaned up, work within the existing RRS transactional context
is rolled back unexpectedly. The following symptom occurs when
WebSphere MQ is delivering a message requiring a native RRS
transaction context:

Local tx completion failed;
com.ibm.ws.LocalTransaction.RolledbackException: Resources
rolled back due to unresolved action of rollback.
at
com.ibm.ws.LocalTransaction.LocalTranCoordImpl.cleanup(LocalTran
CoordImpl.java:1371)
at
com.ibm.ws.LocalTransaction.LocalTranCoordImpl.end(LocalTranCoor
dImpl.java:1419)
at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:889)
at com.ibm.ejs.csi.BeanManaged.postInvoke(BeanManaged.java:362)
at
com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionCon
trolImpl.java:561)
at
com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:
4549)
at
com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:107)
at
com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:132)
at
com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBWrapper.java:24
2)
at
com.ibm.ejs.jms.listener.WS390ServerSession.onMessage(WS390Serve
rSession.java:366)
at
com.ibm.ejs.jms.listener.WS390ServerSession.runMR(WS390ServerSes
sion.java:213)
at
com.ibm.ejs.jms.listener.MDBCppUtilitiesInterfaceImpl.onMessageR
eference(MDBCppUtilitiesInterfaceImpl.java:253)
at
com.ibm.ws390.mdb.MDBCppUtilities.onMessageReference(MDBCppUtili
ties.java:153)
at
com.ibm.ws390.orb.CommonBridge.nativeRunApplicationThread(Native
 Method)
at
com.ibm.ws390.orb.CommonBridge.runApplicationThread(CommonBridge
.java:460)
at
com.ibm.ws.util.ThreadPool$ZOSWorker.run(ThreadPool.java:1724)

Problem conclusion

Apply APAR PM06658 to enable the server to create native RRS
local transaction contexts within WebSphere Application Server
z/OS local transactions over RRS-capable resources.

The fix for this APAR is currently targeted for inclusion in
fix pack 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
PM06658
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-02
Closed date
2010-04-21
Last modified date
2010-04-21

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

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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM06658: TRIGGER CREATION OF RRS NATIVE LTC FOR UNSHARABLE CONN IN BMT

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

R700 PSY

Document Information

Share your feedback

Need support?