Intermittent XAER_RMERR on Start Branch/ getConnection()

Question

Hello,
I've been reading the forums on and off for a couple months now. I was hoping someone could help me with a problem I am facing.
I have a Container Managed MDB that persists a message in a DB. I am able to successfully complete a XA Transaction and my DB is setup for XA. I am running Weblogic 8 sp3 and connecting to a Oracle 8.1.7 DB using Oracle 9.0.2 drivers (due to integration reasons).
I ocassionally get the following error. I have "Test Connections on Reserve" and "Test Connections on Release" both checked. My initial Pool size is 0 and I have shrinking allowed. Any thoughts?
javax.ejb.EJBException: nested exception is: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start() failed on resource 'SMHPMEConnectionPool': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException: Unexpected error during start for XAResource 'SMHPMEConnectionPool': Transaction timed out after 61 seconds
Xid=BEA1-20C1A39CB54A5585B43F(32612847),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=61,seconds left=60,XAServerResourceInfo[JMS_SMHPMEJDBCStore]=(ServerResourceInfo[JMS_SMHPMEJDBCStore]=(state=started,assigned=none),xar=JMS_SMHPMEJDBCStore,re-Registered = false),SCInfo[MLIM+mlimManaged2]=(state=active),local properties=({weblogic.jdbc.jta.SMHPMEConnectionPool=weblogic.jdbc.wrapper.TxInfo@be676c}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=mlimManaged2+jasweblp.mlam.ml.com:9104+MLIM+t3+, XAResources={},NonXAResources={})],CoordinatorURL=mlimManaged2+jasweblp.mlam.ml.com:9104+MLIM+t3+)
     at weblogic.jdbc.wrapper.XA.createException(XA.java:104)
     at weblogic.jdbc.jta.DataSource.start(DataSource.java:678)
     at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1103)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1035)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:213)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:461)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1383)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1325)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:396)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:354)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
     at com.ml.mlim.smh.pme.portfolio.j2ee.PMEPortfolioBean.getConnection(Unknown Source)
     at com.ml.mlim.smh.pme.portfolio.j2ee.PMEPortfolioBean.init(Unknown Source)
     at com.ml.mlim.smh.pme.portfolio.j2ee.PMEPortfolioBean.onMessage(Unknown Source)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Answer 1

You might try upping your JTA Transaction Timeout as well
as XASetTransactionTimeout and XATransactionTimeout; the
latter have to be set manually in the config.xml.
I believe we had similar problems with long-running txns,
and this fixed it.
: jay