Getting TXN timeout exception when getting an XA Oracle Database Connection

Question

Running WLS 8.1 sp5 on Linux in a Cluster (4 servers)
          Using Oracle 10.2.0.2.0 Thin XA driver
          Running Oracle Datbase 9.2.06 or 9.2.07; I think
          I am getting the SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 31 seconds
          It fails at: weblogic.jdbc.jta.DataSource.enlist(Lweblogic/transaction/Transaction;)V(Optimized Method). The exception occurs on all 4 WLS instances at the same time.
          Stack trace at bottom. This problem seems to occur on and off at about the same time. We have not been able to see other jobs that would affect it during this time.
          - Max Pool Size = 25
          - Current and High Connections = 5
          - Num Unavaiable = 0
          - Failure to Reconnect = 0
          - Connection Delay ranges from 57 to 126 milliseconds
          The problem occurs within an MDB. The MDB gets a msg from the JMS queue, fires off an SMTP msg, and tries to update the database and fails due to the timeout on enlisting in the XA transaction.
          Any thoughts on what to look for? Read the info at http://edocs.bea.com/wls/docs81/faq/JTA.html#738205. Is it talking to the Oracle database to enlist. Since occuring on all 4, there is a central place it's failing and I guess the database is a start.
          Thanks. Later...
          - Wayne
          Wed Jan 10 08:30:13 EST 2007: EMS: Exception: EMSSenderDao.mdbChangeMessageQueueStatus() : java.lang.Exception: getMdbDBConnection() : java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 31 seconds
          BEA1-6A0F2B6B5AA26811FBB9
          at weblogic.jdbc.jta.DataSource.enlist(Lweblogic/transaction/Transaction;)V(Optimized Method)
          at weblogic.jdbc.jta.DataSource.getConnection()Ljava/sql/Connection;(Optimized Method)
          at weblogic.jdbc.jta.DataSource.connect(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;(Optimized Method)
          at weblogic.jdbc.common.internal.RmiDataSource.getConnection()Ljava/sql/Connection;(Optimized Method)
          at com.foo_company.ems.dao.EMSSenderDao.mdbChangeMessageQueueStatus(ILjava/lang/String;I)I(Optimized Method)
          at com.foo_company.ems.ejb.emsmessageconsumer.EMSMessageConsumerBean.onMessage(Ljavax/jms/Message;)V(Optimized Method)
          at weblogic.ejb20.internal.MDListener.execute(Lweblogic/kernel/ExecuteThread;)V(Optimized Method)
          at weblogic.ejb20.internal.MDListener.transactionalOnMessage(Ljavax/jms/Message;)V(Optimized Method)
          at weblogic.ejb20.internal.MDListener.onMessage(Ljavax/jms/Message;)V(Optimized Method)
          at weblogic.jms.client.JMSSession.onMessage(Ljavax/jms/MessageListener;Lweblogic/jms/common/MessageImpl;)V(Optimized Method)
          at weblogic.jms.client.JMSSession.execute(Lweblogic/kernel/ExecuteThread;)V(Optimized Method)
          at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)
          at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)
          at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)

Answer 1

Wayne Lau wrote:
          > Running WLS 8.1 sp5 on Linux in a Cluster (4 servers)
          > Using Oracle 10.2.0.2.0 Thin XA driver
          > Running Oracle Datbase 9.2.06 or 9.2.07; I think
          >
          > I am getting the SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 31 seconds
          >
          > It fails at: weblogic.jdbc.jta.DataSource.enlist(Lweblogic/transaction/Transaction;)V(Optimized Method). The exception occurs on all 4 WLS instances at the same time.
          >
          > Stack trace at bottom. This problem seems to occur on and off at about the same time. We have not been able to see other jobs that would affect it during this time.
          > - Max Pool Size = 25
          > - Current and High Connections = 5
          > - Num Unavaiable = 0
          > - Failure to Reconnect = 0
          > - Connection Delay ranges from 57 to 126 milliseconds
          >
          > The problem occurs within an MDB. The MDB gets a msg from the JMS queue, fires off an SMTP msg, and tries to update the database and fails due to the timeout on enlisting in the XA transaction.
          >
          > Any thoughts on what to look for? Read the info at http://edocs.bea.com/wls/docs81/faq/JTA.html#738205. Is it talking to the Oracle database to enlist. Since occuring on all 4, there is a central place it's failing and I guess the database is a start.
          >
          > Thanks. Later...
          >
          >
          > - Wayne
          Hi. At that moment the issue, whatever it is, has already happened.
          Something in the processing of the transaction to this point has
          already taken longer than you have specified that a transaction
          must complete in. Ideally we'd like to see the JTA/JDBC/2PC debug
          logging turned on, so we have lines with timestamps for every
          step in your tx.
          Joe
          > Wed Jan 10 08:30:13 EST 2007: EMS: Exception: EMSSenderDao.mdbChangeMessageQueueStatus() : java.lang.Exception: getMdbDBConnection() : java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 31 seconds
          > BEA1-6A0F2B6B5AA26811FBB9
          > at weblogic.jdbc.jta.DataSource.enlist(Lweblogic/transaction/Transaction;)V(Optimized Method)
          > at weblogic.jdbc.jta.DataSource.getConnection()Ljava/sql/Connection;(Optimized Method)
          > at weblogic.jdbc.jta.DataSource.connect(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;(Optimized Method)
          > at weblogic.jdbc.common.internal.RmiDataSource.getConnection()Ljava/sql/Connection;(Optimized Method)
          > at com.foo_company.ems.dao.EMSSenderDao.mdbChangeMessageQueueStatus(ILjava/lang/String;I)I(Optimized Method)
          > at com.foo_company.ems.ejb.emsmessageconsumer.EMSMessageConsumerBean.onMessage(Ljavax/jms/Message;)V(Optimized Method)
          > at weblogic.ejb20.internal.MDListener.execute(Lweblogic/kernel/ExecuteThread;)V(Optimized Method)
          > at weblogic.ejb20.internal.MDListener.transactionalOnMessage(Ljavax/jms/Message;)V(Optimized Method)
          > at weblogic.ejb20.internal.MDListener.onMessage(Ljavax/jms/Message;)V(Optimized Method)
          > at weblogic.jms.client.JMSSession.onMessage(Ljavax/jms/MessageListener;Lweblogic/jms/common/MessageImpl;)V(Optimized Method)
          > at weblogic.jms.client.JMSSession.execute(Lweblogic/kernel/ExecuteThread;)V(Optimized Method)
          > at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)
          > at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)
          > at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)