Ejb is participating in transaction even when ejb method is created with NOT_SUPPORTED when invoked from client which is in transaction

(Doc ID 1330198.1)

Last updated on MARCH 01, 2018

Applies to:

Oracle Weblogic Server - Version 10.0 and later
Information in this document applies to any platform.



EJB1(TransactionAttributeType.REQUIRED) --Invokes--> EJB2(TransactionAttributeType.NOT_SUPPORTED)

Both 2 ejbs are running under the Container-Managed Transactions

EJBApplication-A --> @TransactionAttribute(TransactionAttributeType.REQUIRED) ---> deployed to Managed Server
EJBApplication-B --> @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) ---> deployed to Admin Server

EJBApplication-B is sleeping for 40 secs.

When EJBApplication-A invokes EJBApplication-B the transaction is getting Propagated to EJBApplication-B even when specified NOT_SUPPORTED.

1.) Why the transaction is getting propagated from one server to other server?
2.) But why is the transaction getting timed out? This is happening due time to live of the transaction is still elapsing waiting for any work done in EJBApplication-B (Since EJBApplication-B is in sleep mode for 40 secs)?

javax.ejb.EJBException: nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds

weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1731)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1606)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1863)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1516)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)


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