MQSeries.net :: View topic - Big Troble Help

chauhan_vin1 · Posted: Tue Jul 14, 2009 9:15 am Post subject: Big Troble Help - J2CA0027E

Hi All,

I have a J2EE application comprising of Stateless session beans and MDB's, We have deployed these on Websphere Process Server 6.0.2.5

The messaging for WPS is on Websphere MQ on Z/OS.We sometimes face some XA errors with respect to MQ.

[7/14/09 9:42:38:987 PDT] 00000059 ImportServlet I com.clear2pay.bph.opf.logging
[7/14/09 9:42:38:989 PDT] 00000059 ImportServlet I com.clear2pay.bph.opf.logging
[7/14/09 9:42:39:186 PDT] 0000005a XATransaction E J2CA0027E: An exception occ
JMSManagedConnection@194476453, within transaction ID {XidImpl: formatId(5741534
9ec0588062b4c152a8f24de408b033938e658132000001227a24f8ae0000000100000d5a9ec05880
.transaction.xa.XAException: XA operation failed, see errorCode
at com.ibm.mq.MQXAResource.start(MQXAResource.java:447)
at com.ibm.ejs.jms.JMSManagedSession$JMSXAResource.start(JMSManagedSessi
at com.ibm.ejs.j2c.XATransactionWrapper.start(XATransactionWrapper.java(
at com.ibm.ws.Transaction.JTA.JTAResourceBase.start(JTAResourceBase.java
at com.ibm.ws.Transaction.JTA.RegisteredResources.startRes(RegisteredRes
at com.ibm.ws.Transaction.JTA.RegisteredResources.enlistResource(Registe
at com.ibm.ws.Transaction.JTA.TransactionImpl.enlistResource(Transaction
at com.ibm.ws.Transaction.JTA.TranManagerSet.enlist(TranManagerSet.java(
at com.ibm.ejs.j2c.XATransactionWrapper.enlist(XATransactionWrapper.java
at com.ibm.ejs.j2c.ConnectionEventListener.interactionPending(Connection
at com.ibm.ejs.jms.JMSManagedSession.interactionPending(JMSManagedSessio
at com.ibm.ejs.jms.JMSManagedSession.enlist(JMSManagedSession.java:909)
at com.ibm.ejs.jms.JMSSessionHandle.enlist(JMSSessionHandle.java:1002)
at com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:6
at com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:59
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java(Compiled Code))
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java(Compiled Code))
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at com.ibm.ejs.jms.listener.ServerSessionDispatcher.dispatch(ServerSessi
onDispatcher.java:37)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:91)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:127)
at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:479)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
.
[7/14/09 9:42:39:222 PDT] 0000005a RegisteredRes E WTRN0078E: An attempt by th
e transaction manager to call start on a transactional resource has resulted in
an error. The error code was XAER_RMERR. The exception stack trace follows: java
x.transaction.xa.XAException: XA operation failed, see errorCode
at com.ibm.mq.MQXAResource.start(MQXAResource.java:447)
at com.ibm.ejs.jms.JMSManagedSession$JMSXAResource.start(JMSManagedSessi
on.java:1318)
at com.ibm.ejs.j2c.XATransactionWrapper.start(XATransactionWrapper.java(

at com.ibm.ws.Transaction.JTA.JTAResourceBase.start(JTAResourceBase.java(Compiled Code))
... 21 more
while trying to enlist resources from datasource JMS$QCF$JMSManagedConnection@194476453 with the Transaction Manager for the current transaction, and threw
a ResourceException.
[7/14/09 9:42:39:281 PDT] 0000005a ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resour
ce JMS$QCF$JMSManagedConnection@194476453. The exception which was received is javax.jms.JMSException: Enlist failed
[7/14/09 9:42:39:284 PDT] 0000005a ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resour
ce jms/QCF. The exception which was received is javax.jms.JMSException: Enlist failed
[7/14/09 9:42:39:316 PDT] 0000005a JMSExceptionL E WMSG0018E: Error on JMSConnection for MDB ImportListenerMDB , JMSDestination jms/ImportQ : javax.jms.JM
SException: Enlist failed
at com.ibm.ejs.jms.JMSCMUtils.mapToJMSException(JMSCMUtils.java:135)
at com.ibm.ejs.jms.JMSManagedSession.enlist(JMSManagedSession.java:931)
at com.ibm.ejs.jms.JMSSessionHandle.enlist(JMSSessionHandle.java:1002)
at com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:611)
at com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:594)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at com.ibm.ejs.jms.listener.ServerSessionDispatcher.dispatch(ServerSessionDispatcher.java:37)
=============================================

The ImportMDB used the ImportListener from the logs we see that the listener restarted , and processed the message , but sometime the listener doesn not even start , and why are these errors coming.

Our WPS is on Linux , when we try to see the TCP connection to MQ from WPS using : ps -ef | grep 1545

We see one of the connection to MQ in CLOSE_WAIT state , why is it going on close wait . We have enabled MQDISCNT setting on MQ side , so initially we thought the MQ is doing a disconnect and the connection on WPS side is not aware of that disconnect.

So to combat that we enabled KeepAlive on MQ : currenlty we are at

HIBINT = 300
KeepAlive = 600
MQDISCNT = 1800

This also is not helping , do we need to tune the keepalive setting also on the Linux OS , which is currenlty at 2 hours.

Please let me know how to resolve this error, what should I tell my MQ guys to do , if MQ people disable MQ disconnect i.e MQDICNT = 0 we are not seeing this issue. But they dont want to disable this setting