WebLogic Tuxedo Connector(also known as WTC) TBRIDGE stop working with javax.transaction.NotSupportedException (Doc ID 2091933.1)

Last updated on MAY 02, 2017

Applies to:

Oracle WebLogic Server - Version 10.3 to 12.1.3.0.0
Information in this document applies to any platform.

Symptoms

1. On Weblogic 10.3.0 version, WTC with tbridge stoped working after network issue. While restarting of WLS server the below exception appears on server log:

javax.transaction.NotSupportedException: Another transaction is associated with this thread. Existing transaction Name=WTC,Xid=BEA1-0004B0A5EA1E(2102716785),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=5,seconds left=55,activeThread=Thread[Thread-27,5,Pooled Threads],SCInfo[mydomain+myops_gateway]=(state=active),properties=({weblogic.transaction.name=WTC}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myops_gateway+myhost:12345+mydomain+t3+, XAResources={WLStore_mydomain_myops FileStore, XADATASC, OatmialResource, WLStore_mydomain_MYOPSDOXFILESTORE},NonXAResources={})])
  at weblogic.transaction.internal.TransactionManagerImpl.internalBegin(TransactionManagerImpl.java:214)
  at weblogic.transaction.internal.ServerTransactionManagerImpl.internalBegin(ServerTransactionManagerImpl.java:357)
  at weblogic.transaction.internal.ServerTransactionManagerImpl.begin(ServerTransactionManagerImpl.java:322)
  at weblogic.wtc.tbridge.tBexec.tuxQ2jmsQ(Unknown Source)
  at weblogic.wtc.tbridge.tBexec.run(Unknown Source)


2. Similar exception can be seen only on Weblogic 12.1.3 if qname length is bigger than 11. On older WLS versions 12.1.1.1 or 12.1.2 this issue is not seen:
javax.transaction.NotSupportedException: Another transaction is associated  with this thread. Existing transaction  Name=WTC,Xid=BEA1-000AAFAB0FED(1204026663),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=5,seconds
left=55,useSecure=false,activeThread=Thread[Thread-46,5,Pooled  Threads],SCInfo[wtc1213+AdminServer]=(state=active),properties=({weblogic.tran saction.name=WTC}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescripto  r=(CoordinatorURL=AdminServer+mylochost:7001+wtc1213+t3+ CoordinatorNonSecureURL=AdminServer+mylochost:7001+wtc1213+t3+ coordinatorSecureURL=AdminServer+mylochost:7002+wtc1213+t3s+, XAResources={WSATGatewayRM_AdminServer_wtc1213, OatmialResource, WLStore_wtc1213_FileStore-0},NonXAResources={})])

OR

will get an ArrayIndexOutOfBoundsException when making the TuxedoConnection.tpenqueue call, like below:

03/02 18:06:06.631 CoreServer0.2429 SEVERE SlrQueueBean.onMessage:124 Unexpected exception - [ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'
java.lang.ArrayIndexOutOfBoundsException
at java.lang.System.arraycopy(Native Method)
at com.bea.core.jatmi.common.Utilities.baReadXdrString(Utilities.java:902)
at weblogic.wtc.jatmi.tcm.write_tcm(tcm.java:502)
at weblogic.wtc.jatmi.tfmh.write_tfmh(tfmh.java:714)
at weblogic.wtc.jatmi.dsession._tpacall_internal(dsession.java:3235)
at weblogic.wtc.jatmi.dsession._tpcall_internal(dsession.java:3878)
at weblogic.wtc.jatmi.dsession.tpenqueue(dsession.java:4170)
at weblogic.wtc.gwt.TuxedoConnection.tpenqueue(TuxedoConnection.java:970)
at com.ventyx.servicesuite.util.tuxqueue.TuxQueueSender.enqueue(TuxQueueSender.java:207)
at com.ventyx.servicesuite.util.tuxqueue.TuxQueueSender.post(TuxQueueSender.java:167)
at com.ventyx.servicesuite.util.OqueBuilder.post(OqueBuilder.java:187)
at com.ventyx.servicesuite.slr.SlrQueueBean.notifyFailure(SlrQueueBean.java:160)
at com.ventyx.servicesuite.slr.SlrQueueBean.onMessage(SlrQueueBean.java:118)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:451)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:375)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:310)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4855)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4529)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3976)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:120)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5375)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:548)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
03/02 18:06:06.632 CoreServer0.2429 FINE SlrQueueBean.onMessage:128 EXIT elapsed=42642 - [ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'
03/02 18:06:06.632 CoreServer0.2429 FINE SlrQueueBean.onMessage:129 ------------------------------------------------------- - [ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms