Javax.transaction.RollbackException: Timed out
Hi All,
Using SOA suite 10.1.3.1, I've written an async bpel process that calls a synchronous web service that can sometimes require several minutes to complete. If the process takes longer than about 45 seconds, an exception is logged - javax.transaction.RollbackException: Timed out.
In the process manager console I have set syncMaxWaitTime to 600 (it was initially 45).
I tried to find the <transaction-config timeout=...> value in server.xml. It is not there. If I add the value, it is removed when I stop and start the SOA suite. There is a value in server.xml:
<transaction-manager-config path="transaction-manager.xml" />
In transaction-manager.xml there is an attribute "transaction-timeout" on the transaction-manager element. It was initially set to 30. I changed it to 600 and restarted the SOA suite but the javax.transaction.RollbackException still occurs after about 45 seconds.
Are there other parameters that need to be set to stop this timeout?
Wayne Stielau
Open Text Corporation
The value in transaction-manager.xml was initially 30 not 30000.
I tried setting syncMaxWaitTime=600 and transaction-manager.xml to 600000. Same result.
I tried setting syncMaxWaitTime=600 and transaction-manager.xml to 600.
Also the same result. Transaction timeout is still occurring.
SOA suite was stopped and restarted each time.
I'm going to test on 10.1.2 to see if something possible got broken in 10.1.3.
Similar Messages
-
Javax.transaction.SystemException: Timed out while in 'Logging' state!!!!
Hello, we have an OracleWeblogic 10.3.2 running on a Solaris OS.
In this AppServer we have a FullStack J2EE Application executing distributed transactions that involve 3 manageable resources:
TxDatasource (EJB),
NonTxDatasource with enableTwoPhaseCommit and
JMS
Some of the transactions are timing out while in 'Logging' state and I just cant figure out what the root cause is. As a defensive action I lowered the JTA Timeout seconds because I noticed the 'Logging' phase was taking too long and then timing out. Idea here was not to have too many threads hanging in Logging state and therefore use the JTA Timeout to overcome this problem and minimize impact.
Below, I'm posting a few exceptions thrown in applicaiton log. Any help is very appreciated.
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '175' for queue: 'weblogic.kernel.Default (self-tuning)'> <JG47515> <> <> <1313163611120> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)],Xid=BEA1-7DB913B4CB2B36D47CB7(1248714554),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=82,seconds left=60,XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)]}),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
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:516)
... 2 more
.>
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '154' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1313163611119> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-7DBB13B4CB2B36D47CB7(977835896),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=60,seconds left=60,XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:500)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
... 3 more
.>
This is the stack trace of the thread that hangs while waiting for the lock to write in the transaction file:
"[ACTIVE] ExecuteThread: '64' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x000000010dea3000 nid=0x1e2 in Object.wait() [0xfffffffda03ff000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at weblogic.transaction.internal.ServerTransactionImpl.log(ServerTransactionImpl.java:2005)
- locked <0xfffffffe64964b30> (a weblogic.transaction.internal.ServerTransactionImpl)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2320)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:273)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
- locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
- locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: user8727499 on Aug 12, 2011 11:57 AMHello, we have an OracleWeblogic 10.3.2 running on a Solaris OS.
In this AppServer we have a FullStack J2EE Application executing distributed transactions that involve 3 manageable resources:
TxDatasource (EJB),
NonTxDatasource with enableTwoPhaseCommit and
JMS
Some of the transactions are timing out while in 'Logging' state and I just cant figure out what the root cause is. As a defensive action I lowered the JTA Timeout seconds because I noticed the 'Logging' phase was taking too long and then timing out. Idea here was not to have too many threads hanging in Logging state and therefore use the JTA Timeout to overcome this problem and minimize impact.
Below, I'm posting a few exceptions thrown in applicaiton log. Any help is very appreciated.
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '175' for queue: 'weblogic.kernel.Default (self-tuning)'> <JG47515> <> <> <1313163611120> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)],Xid=BEA1-7DB913B4CB2B36D47CB7(1248714554),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=82,seconds left=60,XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)]}),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
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:516)
... 2 more
.>
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '154' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1313163611119> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-7DBB13B4CB2B36D47CB7(977835896),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=60,seconds left=60,XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:500)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
... 3 more
.>
This is the stack trace of the thread that hangs while waiting for the lock to write in the transaction file:
"[ACTIVE] ExecuteThread: '64' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x000000010dea3000 nid=0x1e2 in Object.wait() [0xfffffffda03ff000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at weblogic.transaction.internal.ServerTransactionImpl.log(ServerTransactionImpl.java:2005)
- locked <0xfffffffe64964b30> (a weblogic.transaction.internal.ServerTransactionImpl)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2320)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:273)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
- locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
- locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: user8727499 on Aug 12, 2011 11:57 AM -
Javax.transaction.RollbackException
Please take few moments to look at this code. I can't see what I am doing wrong. Can you? it is about the RollbackException. the create method inserts a record in de database, but I am not sure if the container rolls it back, or may be the primary key class is not well implemented.
Your help is very appreciated. I am stack here since 3 days ;(
The create method in the Movie_LoanBean
public Movie_LoanKey ejbCreate (int Member,int Movie,int copy_number,java.sql.Date DayDate_Loaned)
throws CreateException {
if (Member == 0 || Movie == 0 || copy_number == 0 || DayDate_Loaned == null ) {
throw new CreateException(
"Rerquired fields are not filled.");
try {
insertMovie_Loan(Member , Movie , copy_number , DayDate_Loaned );
this.Member = Member;
this.Movie = Movie;
this.copy_number = copy_number;
this.DayDate_Loaned = DayDate_Loaned;
return new Movie_LoanKey(Member, Movie, copy_number, DayDate_Loaned);
} catch (Exception e) {
throw new CreateException (e.toString());
private void insertMovie_Loan(int Member,int Movie,int copy_number,java.sql.Date DayDate_Loaned)
throws SQLException {
makeConnection();
System.out.println("in insertMovie_Loan");
String insertStatement = "INSERT INTO Movie_Loan2 VALUES(?, ?, ?, ?)";
PreparedStatement prepStmt = con.prepareStatement(insertStatement);
prepStmt.setInt(1, Member);
prepStmt.setInt(2, Movie);
prepStmt.setInt(3, copy_number);
prepStmt.setDate(4, (java.sql.Date) DayDate_Loaned);
prepStmt.executeUpdate();
prepStmt.close();
System.out.println("leaving insertMovie_Loan");
releaseConnection();
The primary key class
public class Movie_LoanKey implements java.io.Serializable {
public int Member;
public int Movie;
public int copy_number;
public java.sql.Date DayDate_Loaned;
public Movie_LoanKey() {}
public Movie_LoanKey(int Member, int Movie, int copy_number, java.sql.Date DayDate_Loaned) {
this.Member = Member;
this.Movie = Movie;
this.copy_number = copy_number;
this.DayDate_Loaned = DayDate_Loaned;
public int getMember() {
return Member;
public int getMovie() {
return Movie;
public int getcopy_number() {
return copy_number;
public java.sql.Date getDayDate_Loaned() {
return DayDate_Loaned;
public boolean equals (Object obj) {
if ( obj == null || !( obj instanceof Movie_LoanKey ))
return false;
else if ( (((Movie_LoanKey) obj).Member == Member) && (((Movie_LoanKey) obj).Movie == Movie) && (((Movie_LoanKey) obj).copy_number == copy_number) && (((Movie_LoanKey) obj).DayDate_Loaned == DayDate_Loaned) )
return true;
else
return false;
public String toString() {
return String.valueOf(Member) + String.valueOf(Movie) + String.valueOf(copy_number) + DayDate_Loaned.toString() ;
public int hashCode() {
String tmp0 = String.valueOf(Member) ;
String tmp1 = String.valueOf(Movie) ;
String tmp2 = String.valueOf(copy_number) ;
String tmp3 = DayDate_Loaned.toString();
return tmp0.concat(tmp1).concat(tmp2).concat(tmp3).hashCode();
The client
import java.util.*;
import java.math.*;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.rmi.PortableRemoteObject;
public class LoanClient {
public static void main(String[] args) {
try {
Context initial = new InitialContext();
Object objref = initial.lookup("java:comp/env/ejb/SimpleLoan");
Movie_LoanHome home = (Movie_LoanHome) PortableRemoteObject.narrow(objref,
Movie_LoanHome.class);
java.sql.Date d1 = java.sql.Date.valueOf("04-01-05");
Movie_Loan duke = home.create(1,3,4,d1);
System.exit(0);
} catch (Exception ex) {
System.err.println("Caught an exception.");
ex.printStackTrace();
When I run this code I get the following error:
java.rmi.ServerException: RemoteException occurred in server thread; nested exce
ption is:
java.rmi.RemoteException: Transaction aborted; nested exception is: java
x.transaction.RollbackException; nested exception is:
javax.transaction.RollbackException
at com.sun.corba.ee.impl.javax.rmi.CORBA.Util.mapSystemException(Util.ja
va:170)
at javax.rmi.CORBA.Util.mapSystemException(Util.java:65)
at MovieLoanHome_Stub.create(Unknown Source)
at LoanClient.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.util.Utility.invokeApplicationMain(Utility.java:28
5)
at com.sun.enterprise.appclient.Main.<init>(Main.java:420)
at com.sun.enterprise.appclient.Main.main(Main.java:92)
Caused by: java.rmi.RemoteException: Transaction aborted; nested exception is: j
avax.transaction.RollbackException; nested exception is:
javax.transaction.RollbackException
at com.sun.enterprise.iiop.POAProtocolMgr.mapException(POAProtocolMgr.ja
va:213)
at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:79
7)
at com.sun.ejb.containers.EJBHomeInvocationHandler.invoke(EJBHomeInvocat
ionHandler.java:194)It means that your code somewhere throws a system exception.
Have you tried to debug you'r bean ? Run EJB server under an IDE with debugging capabilities (JBuilder, IDEA).
This would speed up your development.
Why do you use a BMP beans ? In this case CMP would work without any problems. -
Javax.transaction.RollbackException: Transaction marked for rollback
Hello all,
This is my first topic/question in the forums. I am relatively novice with J2EE programming so please pardon my ignorance. I have spend several hours thying to figure out the following issue.
So here is the scenario. I have a JSF ManagedBean called SymbolProcessBean. Here is part of its declaration
@PersistenceContext(name = "persistence/LogicalName", unitName = "MantisPU")
public class SymbolProcessBean {
@Resource
private UserTransaction utx;
}The Bean is callef by a h:command from a jsp page
<h:commandLink action="#{symbolProcessBean.processSymbol}" value="Process"/>In part of the process the Bean read data from a webpage and persists them in a MySQL database. Here is the loop:
try {
// Create a URL for the desired page
String urlStr = "http://ichart.finance.yahoo.com/table.csv?s=" + this.selectedSymbol.getTicker();
if (firstNewDay != null)
urlStr += "&a=" + firstNewDay.get(Calendar.MONTH) +
"&b=" + firstNewDay.get(Calendar.DATE) +
"&c=" + firstNewDay.get(Calendar.YEAR);
URL url = new URL(urlStr);
// Read all the text returned by the server
BufferedReader in = new BufferedReader(new InputStreamReader(url.openStream()));
String str;
outText = in.readLine() + "<br />"; // Discard first line
Context ctx = (Context) new InitialContext().lookup("java:comp/env");
utx.begin();
em = (EntityManager) ctx.lookup("persistence/LogicalName");
SimpleDateFormat formatter = new SimpleDateFormat("yyyy-MM-dd");
while ((str = in.readLine()) != null) {
// Use togenizer to parse comma separated fields
StringTokenizer strtok = new StringTokenizer(str, ",");
// Read the data from the line
Date recordDate = formatter.parse(strtok.nextToken());
Float open = Float.valueOf(strtok.nextToken());
Float high = Float.valueOf(strtok.nextToken());
Float low = Float.valueOf(strtok.nextToken());
Float close = Float.valueOf(strtok.nextToken());
Integer volume = Integer.valueOf(strtok.nextToken());
Float adj_close = Float.valueOf(strtok.nextToken());
// Set the PriceRecord data members
PriceRecord pr = new PriceRecord();
pr.setSymbol(this.selectedSymbol);
pr.setRecordDate(recordDate);
pr.setOpen(open);
pr.setHigh(high);
pr.setLow(low);
pr.setClose(close);
pr.setVolume(volume);
pr.setAdjClose(adj_close);
// Create Record
em.persist(pr);
this.selectedSymbol.getPriceRecordCollection().add(pr);
// Add record string to output text
outText += str + "<br />";
in.close();
this.selectedSymbol = em.merge(this.selectedSymbol);
utx.commit();
} catch (Exception e) {
utx.rollback();
throw e;
}All this works fine on the first invocation of the command link and the Bean reads the data from yahoo for a Stock symbol and persists into the database. When the command link is clicked again for a different stock then the utx.commit(); throws a "javax.transaction.RollbackException: Transaction marked for rollback" exception. NOTE that when I redeploy the application and run it again it will work. But it works only the first time. The second time it will throw the exception.
I am not sure why this happens. I looked in the create() methods of the autogenerated JPA Controllers (PriceRecordJpaController) and they allways commit the transaction. Why would it fail in my case? Is there a way to "refresh" the transaction?
Thank you in advance.
Edited by: kkyriako on Nov 11, 2009 10:37 PMThank you for your responses. I had no idea that when a runtime exception is thrown the transaction will be marked for rollback. The getCause of the exception is null however I got the following stack trace from the GlashFish log:
WARNING:
Local Exception Stack:
Exception [EclipseLink-7197] (Eclipse Persistence Services - 1.0.1 (Build 20080905)): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Null primary key encountered in unit of work clone [ejb.entities.PriceRecord[idPriceRecord=null]].
at org.eclipse.persistence.exceptions.ValidationException.nullPrimaryKeyInUnitOfWorkClone(ValidationException.java:1305)
at org.eclipse.persistence.descriptors.changetracking.DeferredChangeDetectionPolicy.calculateChanges(DeferredChangeDetectionPolicy.java:84)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.calculateChanges(UnitOfWorkImpl.java:557)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1320)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.issueSQLbeforeCompletion(UnitOfWorkImpl.java:2848)
at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.issueSQLbeforeCompletion(RepeatableWriteUnitOfWork.java:223)
at org.eclipse.persistence.transaction.AbstractSynchronizationListener.beforeCompletion(AbstractSynchronizationListener.java:157)
at org.eclipse.persistence.transaction.JTASynchronizationListener.beforeCompletion(JTASynchronizationListener.java:68)
at com.sun.enterprise.transaction.JavaEETransactionImpl.commit(JavaEETransactionImpl.java:411)
at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.commit(JavaEETransactionManagerSimplified.java:843)
at com.sun.enterprise.transaction.UserTransactionImpl.commit(UserTransactionImpl.java:198)
at ejb.logic.SymbolProcessBean.accessURLData(SymbolProcessBean.java:165)
at ejb.logic.SymbolProcessBean.processSymbol(SymbolProcessBean.java:182)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.el.parser.AstValue.invoke(AstValue.java:187)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:297)
at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
at javax.faces.component.UICommand.broadcast(UICommand.java:387)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756)
at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:431)
at org.apache.catalina.core.StandardWrapperValve.preInvoke(StandardWrapperValve.java:462)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:139)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:186)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:96)
at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:187)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:142)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:325)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:242)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:180)
at com.sun.grizzly.http.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:633)
at com.sun.grizzly.http.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:570)
at com.sun.grizzly.http.DefaultProcessorTask.process(DefaultProcessorTask.java:827)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:152)
at com.sun.enterprise.v3.services.impl.GlassfishProtocolChain.executeProtocolFilter(GlassfishProtocolChain.java:71)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:67)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:56)
at com.sun.grizzly.util.WorkerThreadImpl.processTask(WorkerThreadImpl.java:325)
at com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:184)SymbolProcessBean.java:165 is the utx.commit(). The idPriceRecord is the primary key of the table. It is an autoincrement field. I do not modify it before the em.persist(pr); statement so it goes as null. However the first time when I execute the commit everything is persisted in the database. When I run a second time for a different symbol then I get the exception until I redeploy the wed site. Maybe the persistence layer does not update the idPriceRecord with the value generated by MySQL. Nuy why does that does not cause a problem the first time? -
Javax.transaction.RollbackException occurs on delete
Hello,
I am using a container managed transaction to add, modify and delete data. On adding, the transaction commits successfully. However, on delete the transaction throws a javax.transaction.RollbackException.
The following is the start of the log file entry:
EJB5018: An exception was thrown during an ejb invocation on [DirBean]
javax.ejb.EJBException: Transaction aborted; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback.
javax.transaction.RollbackException: Transaction marked for rollback.I have checked on the database table foreign key they seem in order.
What might be the cause of the rollbackException since hibernate does not display the content of the nested exception?The value in transaction-manager.xml was initially 30 not 30000.
I tried setting syncMaxWaitTime=600 and transaction-manager.xml to 600000. Same result.
I tried setting syncMaxWaitTime=600 and transaction-manager.xml to 600.
Also the same result. Transaction timeout is still occurring.
SOA suite was stopped and restarted each time.
I'm going to test on 10.1.2 to see if something possible got broken in 10.1.3. -
How to skip javax.transaction.RollbackException Transaction has been mark
I am debugging my testcase for which I inspect objects which consumes time and when I go to next line which calls a localdelegate I get times out exception Is there any way I can inform oc4j to ignore timeout.
Hi ,
It looks like intial context factory is missing in the weblogic-ejb-jar.xml, try to add the following line and see.
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
Rule out any typos, Make sure you have specified the exact names in destination-jndi-name,connection-factory-jndi-name in the weblogic-ejb*.xml file.
Thanks -
Oracle BPEL Server version 10.1.3.1.0
Build: 0
Build time: Mon Oct 09 08:44:49 PDT 2006
Build type: release
Source tag: PCBPEL_10.1.3.1.0_GENERIC_061009.0802
Exception Message:
[javax.transaction.RollbackException]
Timed out
Exception Trace:
javax.transaction.RollbackException: Timed out
at com.evermind.server.ApplicationServerTransaction.checkForRollbackOnlyWhileInCommit(ApplicationServerTransaction.java:582)
at com.evermind.server.ApplicationServerTransaction.doCommit(ApplicationServerTransaction.java:244)
at com.evermind.server.ApplicationServerTransaction.commit(ApplicationServerTransaction.java:130)
at com.evermind.server.ApplicationServerTransactionManager.commit(ApplicationServerTransactionManager.java:433)
at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:132)
at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:57)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
at DomainManagerBean_RemoteProxy_4bin6i8.undeployProcess(Unknown Source)
at com.oracle.bpel.client.BPELDomainHandle.undeployProcess(BPELDomainHandle.java:390)
at undeployProcess.jspService(_undeployProcess.java:122)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:591)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:515)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259)
at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:50)
at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193)
at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198)
at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:131)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:619)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)This is a certification forum
I tend to think your post is significantly mis-directed to the incorrect forum and you need to inquire about being awarded plonker-of-the-day certification :-) (I've won that many times myself).
This is not really my scene but a lookup [http://download.oracle.com/docs/cd/B15904_01/core.1012/b14001/optj2ee.htm#i1017060] might be helpful or might a sidetrack up a blind alley
Probablly posting in one of the categories in : [http://forums.oracle.com/forums/category.jspa?categoryID=193] (Probably OAS - General or maybe OC4J) would good, or have a hunt through the forums for a more suitable one.
Rgds - bigdelboy
Edited by: bigdelboy on 20-Jul-2009 01:49 - Justins suggestions of BPEL would be good too. -
Transaction RollbackException when running OIM's scheduler
Dear all,
When we run the custom scheduler ,we run into the following exception:
Exception when DeleteUser Thor.API.Exceptions.tcAPIException: An exception occurred during transaction completion: ; nested exception is:
javax.transaction.RollbackException: Timed out
at Thor.API.Operations.tcReconciliationOperationsClient.provideDeletionDetectionData(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at Thor.API.Base.SecurityInvocationHandler$1.run(Unknown Source)
at Thor.API.Security.LoginHandler.oracleLoginSession.runAs(Unknown Source)
at Thor.API.Base.SecurityInvocationHandler.invoke(Unknown Source)
at $Proxy14.provideDeletionDetectionData(Unknown Source)
at com.ncgc.oim.connector.UserReconciliation.DeleteUser(UserReconciliation.java:440)
at com.ncgc.oim.connector.UserReconciliation.execute(UserReconciliation.java:220)
at com.thortech.xl.scheduler.tasks.SchedulerBaseTask.run(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionAction.run(Unknown Source)
at Thor.API.Security.LoginHandler.oracleLoginSession.runAs(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown Source)
at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)
Besides, there are about 20000 users in the target system. Thanks in advance!Please check out the SAP note below
Note 1099234 - AA 669 in reporting w/ reporting date in future fiscal year
its seems like a program error...implement the note. -
XA & JMS javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+' not available
Hi, I'm doing a "proof of concept" on XA transaction spanning two servers.
In order to get it as simple as possible I have configured two servers and
deployed the same MDB on both. I'm also only using JMS resources to simplify
the test.
The goal is to send a message to two different JMS servers (each deployed in
a Weblogic server) both coordinated by an XA UserTransaction started in the
client.
The deployed MDB of each server just listens to a topic and prints out the
received TextMessage.
The configuration is as follows:
* Server 1
Domain name: a
Server name: a00
config.xml (extract):
<JMSServer Name="a.a00.JMSServer" PagingStore="a.a00.JMSFileStore"
Store="a.a00.JMSFileStore" Targets="a00">
<JMSTopic JNDIName="xajms.test.Topic" Name="XA JMS Proof of Concept"
StoreEnabled="true"/>
</JMSServer>
<JMSFileStore Directory="config/a/a00.jmsfilestore"
Name="a.a00.JMSFileStore"/>
<JMSConnectionFactory JNDIName="a.a00.JMSConnectionFactory"
Name="a.a00.JMS Connection Factory" Targets="a00"
UserTransactionsEnabled="true" XAConnectionFactoryEnabled="true"/>
* Server 2
Domain name: b
Server name: b00
config.xml (extract):
<JMSServer Name="b.b00.JMSServer" PagingStore="b.b00.JMSFileStore"
Store="b.b00.JMSFileStore" Targets="b00">
<JMSTopic JNDIName="xajms.test.Topic" Name="XA JMS Proof of Concept"
StoreEnabled="true"/>
</JMSServer>
<JMSFileStore Directory="config/b/b00.jmsfilestore"
Name="b.b00.JMSFileStore"/>
<JMSConnectionFactory JNDIName="b.b00.JMSConnectionFactory"
Name="b.b00.JMS Connection Factory" Targets="b00"
UserTransactionsEnabled="true" XAConnectionFactoryEnabled="true"/>
and here is an extract of client code:
068 UserTransaction utx;
069
070 InitialContext ctx1,ctx2;
071
072 System.out.println("Retrieving initial context for server 1");
073 ctx1 = (InitialContext) getInitialContext(SERVER_1,PORT_1);
074
075 System.out.println("Retrieving initial context for server 2");
076 ctx2 = (InitialContext) getInitialContext(SERVER_2,PORT_2);
077
078 utx = (UserTransaction)
ctx1.lookup("javax.transaction.UserTransaction");
079 utx.setTransactionTimeout(30);
080
081 System.out.println("Begining transaction");
082 utx.begin();
083
084 System.out.println("Sending message to server 1");
085 ref.send(ctx1, JMS_FACTORY_1, args[0]);
086
087 System.out.println("Sending message to server 2");
088 ref.send(ctx2, JMS_FACTORY_2, args[0]);
089
090 System.out.println("Ending transaction...");
091 if (args[1].equals("commit"))
092 utx.commit();
093 else
094 utx.rollback();
end the result of executing it from a third machine:
CASE I:
Retrieving initial context for server 1
Retrieving initial context for server 2
Begining transaction
Sending message to server 1
Sending message to server 2
Ending transaction...
javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
not available
Start server side stack trace:
javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
not available
at
weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:965
at
weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:20
0)
at
weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTran
sactionImpl.java:1619)
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:217)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:189)
at
weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
at
weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.transaction.RollbackException: SubCoordinator
'b00+127.0.0.1:7001+b+' not available
Start server side stack trace:
javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
not available
at
weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:965
at
weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:20
0)
at
weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTran
sactionImpl.java:1619)
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:217)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:189)
at
weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
at
weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: SubCoordinator
'b00+127.0.0.1:7001+b+' not available - with nested exception:
[javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
not available]
at
weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
tionImpl.java:1524)
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:265)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:189)
at
weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
at
weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
End server side stack trace
- with nested exception:
[javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
not available
Start server side stack trace:
javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
not available
at
weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:965
at
weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:20
0)
at
weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTran
sactionImpl.java:1619)
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:217)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:189)
at
weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
at
weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
End server side stack trace
at
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
java:85)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:136)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy3.commit(Unknown Source)
at
weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.java:29
4)
at
weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
erImpl.java:247)
at
weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
erImpl.java:240)
at xajms.client.Send2BothTopics.main(Send2BothTopics.java:110)
real 1m6.530s
user 0m1.380s
sys 0m0.050s
If I swap message sending order the output changes to:
CASE II:
Retrieving initial context for server 1
Retrieving initial context for server 2
Begining transaction
Sending message to server 2
Sending message to server 1
Ending transaction...
weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds
Start server side stack trace:
weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1228)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImpl.java:488)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1629)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:451)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1595)
at java.lang.Thread.run(Thread.java:479)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Timed out tx=0:8c9a9deee02fe21e
after 30 seconds
Start server side stack trace:
weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1228)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImpl.java:488)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1629)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:451)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1595)
at java.lang.Thread.run(Thread.java:479)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Timed out tx=0:8c9a9deee02fe21e
after 30 seconds - with nested exception:
[weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds]
at
weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
tionImpl.java:1524)
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:265)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:189)
at
weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
at
weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
End server side stack trace
- with nested exception:
[weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds
Start server side stack trace:
weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1228)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImpl.java:488)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1629)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:451)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1595)
at java.lang.Thread.run(Thread.java:479)
End server side stack trace
at
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
java:85)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:136)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy3.commit(Unknown Source)
at
weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.java:29
4)
at
weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
erImpl.java:247)
at
weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
erImpl.java:240)
at xajms.client.Send2BothTopics.main(Send2BothTopics.java:110)
real 1m32.231s
user 0m1.390s
sys 0m0.030s
not to be said that I have "some" questions about it:
1. Why it doesn't work?
2. Why order of message sending brings two different results?
3. In CASE I:
What is the meaning of the exception "javax.transaction.SystemException:
SubCoordinator 'b00+127.0.0.1:7001+b+' not available"
Why is it using the loopback (127.0.0.1) ip? Is that code being runned
inside the server with the SERVER_2 (192.168.1.3) ip?
4. In case II:
How is that the message of the exception is
"weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds" when it's clear the program took
more than one and a half minutes to execute?
Most of the time is spent after printing the "Ending transaction..." line.
The first part of the program is executed in a few seconds (about 2 or 3 it
depends of the time to get initial context against both servers)
I'm really puzzled with this. I don't know what to think about it. Is this
so weird nobody have tried something like this?
I have done some other test for which the results are:
a) Commenting lines related to UserTransaction (82,91-94)
It works OK. Both servers receive the message.
b) Commenting lines 85 or 88 (related to sending messages to each server)
It works OK. Both servers receive the message. I pressume there is no
"real" XA transaction as there is only one resource involved on it.
c) In CASE I launching the client with "rollback" as second parameter I
neither get any exception nor messages are delivered which would be OK
d) In CASE II launching the client with "rollback" as second parameter I get
a "javax.transaction.SystemException: Timeout during rollback processing"
and messages are not delivered.
Any idea?. I really need this to work in order to free our server for heavy
asyncronous loads and deploy new stuff on it.
PS.
I attach both servers config.xml files and both MDB and client full code. If
you are going to test it you must add a new user and group to weblogic
default file realm:
New user: subscriber
New group: xajms
of course you must add the new user to the new group in order to make it
work.
Here are the lines extracted from server's domain "fileRealm.properties"
file reflecting the new user and group (defined on ejb-jar.xml and
weblogic-ejb-jar.xml files on the "role" section):
group.xajms=subscriber
user.subscriber=0x6b9a704bebc709dd083edd61ed000236eb23987f
The client receives two parameters. The first one is a string to be sent as
message body, the second one is either "commit" or "rollback" just to test
XA transaction doing it's work as expected.
Thanks in advance.
Regards.
Ignacio.
[xajmspoc.zip]
do you connect to 10g database inside onBusinessEvent using Non-XA/XA connection??. I guess it could be bcoz of Non-XA connection (or) XA Without Global Transaction support, and this connection is listed with the transaction manager and it is trying to commit it after onMessage.
For Global Transactions options, go to your weblogic console and check the following path.
(Datasource -> Advanced Options -> Global Transactions -> Honor Global Transactions should be true)
Let me know if you need any help
Rao Kotha. -
Javax.transaction.TransactionRolledbackException
Hi
I am getting a weblogic.ejb.extensions.LockTimedOutException when a call an entity bean for the second time. The first time I call the account entity bean from a session bean it returns all the accounts without any problems. However the next time I call the same bean from the same session I get a time out error. It seems to get as far as the last record and the locks. It also seems to use the same context for the last record as it did on the first read. See bold ctx. I have tried changing the isolation level of the beans and increasing the time out limit. I've attached the output below. Has anyone any suggestion.
Thanks
Claire
1st Read from Session Bean
After creating Data Packets601212 ::69000512
before find by account
after find by accountEJBObject: '-915484003', home: 'eon.common.Account', ctx: '-916794723', pk: 'com.bankframe.common.ejb.account.interfaces.AccountPK@64476f25'
accountDp{Account Balance=13010.7, Uncleared Funds=600.0, DATA PACKET NAME=ACCOUNT, OWNER=eontec Ltd, REQUEST_ID=00000, Currency=IEP, Debit Or Credit Balance=Credit, Account Number=69000512, Account T
ype=Chequing, Account Name=Current Account - No. 1, Sort Code=601212}
After creating Data Packets601212 ::77264300
before find by account
after find by accountEJBObject: '1776210589', home: 'eon.common.Account', ctx: '1775948445', pk: 'com.bankframe.common.ejb.account.interfaces.AccountPK@661c2d9f'
accountDp{Account Balance=2100.0, Uncleared Funds=0.0, DATA PACKET NAME=ACCOUNT, OWNER=eontec Ltd, REQUEST_ID=00000, Currency=GBP, Debit Or Credit Balance=Credit, Account Number=77264300, Account Type
=Deposit, Account Name=Term Deposit - Sterling, Sort Code=601212}
2nd Reand from Session Bean
After creating Data Packets601212 ::69000512
before find by account
after find by accountEJBObject: '704303773', home: 'eon.common.Account', ctx: '700895901', pk: 'com.bankframe.common.ejb.account.interfaces.AccountPK@64476f25'
accountDp{Account Balance=13010.7, Uncleared Funds=600.0, DATA PACKET NAME=ACCOUNT, OWNER=eontec Ltd, REQUEST_ID=00000, Currency=IEP, Debit Or Credit Balance=Credit, Account Number=69000512, Account T
ype=Chequing, Account Name=Current Account - No. 1, Sort Code=601212}
After creating Data Packets601212 ::77264300
before find by account
after find by accountEJBObject: '1776210589', home: 'eon.common.Account', ctx: '1775948445', pk: 'com.bankframe.common.ejb.account.interfaces.AccountPK@661c2d9f'
Thu Nov 23 09:45:57 GMT 2000:<I> <TX> Transaction (TxC (650302109, xid = 974971491652_10, timeout = 300, txState = Marked Rollback, root = null) rolled back after 300 sec.
FinderException weblogic.ejb.extensions.LockTimedOutException: Lock for primaryKey:com.bankframe.common.ejb.account.interfaces.AccountPK@661c2d9f timed out after 300000 ms.
finished creating dp
CustomerOverviewBean::processDataPacket()::Sending Result to the Client Excep
{DATA PACKET NAME=CUSTOMER OVERVIEW EXCEPTION, OWNER=eontec Ltd, REQUEST_ID=00000, Reason=javax.transaction.TransactionRolledbackException: Transaction: '974971491652_10' has been rolled back}
Thu Nov 23 09:46:00 GMT 2000:<I> <EJB JAR deployment ./classes/castaway-jars/customeroverview.jar> Exception during commit of transaction: '974971491652_10'
javax.transaction.RollbackException: Transaction TxC (650302109, xid = 974971491652_10, timeout = 0, txState = Rolledback, root = null has been rolled back.Reason: Transaction (TxC (650302109, xid = 9
74971491652_10, timeout = 300, txState = Marked Rollback, root = null) rolled back after 300 sec.
at weblogic.jts.internal.CoordinatorImpl.throwRollbackException(CoordinatorImpl.java:727)
at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:352)
at weblogic.jts.internal.TxContext.commit(TxContext.java:246)
at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:88)
at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java, Compiled Code)
at com.bankframe.bs.customer.ejb.customeroverview.server.CustomerOverviewBeanEOImpl.processDataPacket(CustomerOverviewBeanEOImpl.java:107)
at com.bankframe.bs.customer.ejb.customeroverview.server.CustomerOverviewBeanEOImpl_ServiceStub.processDataPacket(CustomerOverviewBeanEOImpl_ServiceStub.java, Compiled Code)
at com.bankframe.ei.servlet.BankframeServlet.getResponseDataPackets(BankframeServlet.java:173)
at com.bankframe.ei.servlet.BankframeServlet.doGet(BankframeServlet.java:74)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java, Compiled Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java, Compiled Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java, Compiled Code)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java, Compiled Code)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java, Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java, Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
Thu Nov 23 09:46:00 GMT 2000:<I> <ServletContext-General> BankframeServlet: Thu Nov 23 09:46:00 GMT 2000::BankframeServlet::Error in method getResponseDataPackets, the data packet was: {Customer Numbe
r=996324364, DATA PACKET NAME=LIST CUSTOMER ACCOUNTS, OWNER=EON Technologies Ltd, Last Logged Date=20/02/2000, REQUEST_ID=80031}
Thu Nov 23 09:46:00 GMT 2000:<I> <ServletContext-General> BankframeServlet: Thu Nov 23 09:46:00 GMT 2000::BankframeServlet::Unexpected exception in com.bankframe.bs.customer.ejb.customeroverview.serve
r.CustomerOverviewBean.processDataPacket():
javax.transaction.RollbackException: Transaction TxC (650302109, xid = 974971491652_10, timeout = 0, txState = Rolledback, root = null has been rolled back.Reason: Transaction (TxC (650302109, xid = 9
74971491652_10, timeout = 300, txState = Marked Rollback, root = null) rolled back after 300 sec.
at weblogic.jts.internal.CoordinatorImpl.throwRollbackException(CoordinatorImpl.java:727)
at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:352)
at weblogic.jts.internal.TxContext.commit(TxContext.java:246)
at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:88)
at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java, Compiled Code)
at com.bankframe.bs.customer.ejb.customeroverview.server.CustomerOverviewBeanEOImpl.processDataPacket(CustomerOverviewBeanEOImpl.java:107)
at com.bankframe.bs.customer.ejb.customeroverview.server.CustomerOverviewBeanEOImpl_ServiceStub.processDataPacket(CustomerOverviewBeanEOImpl_ServiceStub.java, Compiled Code)
at com.bankframe.ei.servlet.BankframeServlet.getResponseDataPackets(BankframeServlet.java:173)
at com.bankframe.ei.servlet.BankframeServlet.doGet(BankframeServlet.java:74)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java, Compiled Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java, Compiled Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java, Compiled Code)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java, Compiled Code)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java, Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java, Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
; nested exception is:
javax.transaction.RollbackException: Transaction TxC (650302109, xid = 974971491652_10, timeout = 0, txState = Rolledback, root = null has been rolled back.Reason: Transaction (TxC (650302109,
xid = 974971491652_10, timeout = 300, txState = Marked Rollback, root = null) rolled back after 300 sec.
What versions of the WebLogic you are using at windows and unix machines ? What are transaction attributes of the EJB methods you are invoking ?
-
Receiving Transaction Manager Time out in iProcurement Receiving!
Hi All,
Database:10.2.0.4.0
Oracle Aps:12.0.6
O/S:AIX 64 bits 5.3 L
We are unable to create any receipts due to following error.Checked Receiving Transaction Manager and that is running fine.
Error Message
Your receipt could not be created successfully because your receiving transaction manager timed out.
Please contact your System Administrator for further assistance.
Steps To Reproduce
The issue can be reproduced at will with the following steps:
1. In Iprocurement select requisition to receive
2. Enter required data and press submit
3. on screen receive Items: review and submit get above error message
Profile RCV: Processing Mode is currently set to 'online'
Could anyone please share resolution to such an issue faced before.
Thanks for your time!
Regards,Follow the Metalink ID: 375152.1
-
Users timing out in Oracle AS 10.1.3
I am trying to figure out why the load tests running in the target environment (large and very secure corporate network) against a Spring MVC/EJB3 application running in Orcale AS 10.1.3 fail. The application is deployed on a server running on a Solaris Sparc 440 machine.
The tests are run from LoadRunner application, which simulates multiple users sending HTTP requests to perform a use case in the system under test. The use case involves transitioning between 4 different pages with the application sending a number (relatively small, 5-6 pr use case) of queries to the Oracle database running on a different machine (using JPA/TopLink) and doing a single insert.
The LoadRunner shows that after a few minutes after the test starts the users start timing out. The HTTP request sent to the application server (with timeout value of two minutes) do not get fulfilled.
I have looked at various performance metrics: CPU and memory utilization on the Solaris machine, metrics provided by the Oracle AS admin console (JVM Heap memory usage, number of EJB methods per second, number of servlet requests per second and request processing time. Nothing indicates a bottleneck. The application uses much less memory than is allocated (100MB out of 2GB allowed), the CPU and memory utilization on the machine are within norm. The EJB methods execute in a fraction of a second (nothing to justify a two-minute delay).
An interesting aspect of the test is the effect of the static resources on the performance. About two thirds of HTTP request in the test are for static resources (GIFs and CSS). They are not being cached by the HTTP server. Two similar LoadRunner tests were performed. In one, all HTTP requests were submitted (20 users running 10 iterations each). In the second, LoadRunner itself cached the static resources, thus submitting only the requests processed by Spring MVC portion of the Java application (the same number of users and iterations). The second tests produced a much lower timeout rate. (Out of 218 transactions, 34 timed out in the first test and 2 in the second).
I am trying to understand what may cause the timeouts in these tests. The most obvious culprit is the Java application being tested, but if the bottleneck was in Java, then caching static resources would have almost no effect on the performance results (since static resources do not go to the Java application).
I tested the same application using Apache JMeter in the development environment (a small company network) with Oracle AS running on Solaris VM (itself running on a Windows machine, which is less powerful than the Sparc 440 machine). The test running exactly the same use case with 20 users running 200 iterations each went without a single hiccup. Not a single HTTP request timed out and the mean request time was 69 ms.
I am looking for help in finding the causes for the performance issues in the target environment and why they cannot be replicated in the development environment. What may be causing the simulated users to time out?
Thank you,
MichaelYes OHS (Oracle HTTP Server) comes with PHP pre-installed and ready to use. Refer following for details:
http://download.oracle.com/docs/cd/B32110_01/web.1013/b28948/php.htm#BABIGCFB
Thanks
Shail -
Update operation transaction timing out
Hello,
I have a large data structure that needs to be updated atomically (i.e. within a transaction). I am calling the logical service via a web service map, so I presume the transaction starts when the logical service is invoked. It is receiving a transaction timeout on the server, which I suspect is set to 30 seconds at the WebLogic level by our middleware team. (See stack trace below).
The update operation SDO XML is at least 2MB.
1. Is there any way to override this transaction timeout at the service or data space level?
2. Is there any more efficient way to do this update? Sending a big wad of xml is inefficient, and I am not aware of another format supported by ODSI web services. I cannot use mediator API straight from my client to ODSI.
3. If I have to break up my save operation into chunks, is there any way to effectively achieve transactional update via multiple web service calls?
Any advice would be much appreciated.
Thanks,
Jeff
weblogic.xml.query.exceptions.XQuerySystemException: {bea-err}SYS003: Unexpected exception
at weblogic.xml.query.transaction.TransactionHelper.commit(TransactionHelper.java:96)
at weblogic.xml.query.transaction.TransactionManager.teardownOnSuccess(TransactionManager.java:178)
at com.bea.ld.EJBRequestHandler.handleProcessingComplete(EJBRequestHandler.java:1020)
at com.bea.ld.EJBRequestHandler.handlePusher(EJBRequestHandler.java:979)
at com.bea.ld.EJBRequestHandler.invokeOperation(EJBRequestHandler.java:323)
at com.bea.ld.ServerWrapperBean.invoke(ServerWrapperBean.java:153)
at com.bea.ld.ServerWrapperBean.invokeOperation(ServerWrapperBean.java:80)
at com.bea.ld.ServerWrapper_s9smk0_ELOImpl.invokeOperation(ServerWrapper_s9smk0_ELOImpl.java:141)
at com.bea.dsp.ws.RoutingHandler$PriviledgedRunner.run(RoutingHandler.java:96)
at com.bea.dsp.ws.RoutingHandler.handleResponse(RoutingHandler.java:217)
at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:287)
at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:271)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:176)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:285)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:169)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.transaction.RollbackException: Transaction timed out after 33 seconds
BEA1-460E808DE23C779E385F
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1818)
at weblogic.transaction.internal.TransactionImpl.checkIfCommitPossible(TransactionImpl.java:1708)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:255)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:230)
at weblogic.xml.query.transaction.TransactionHelper.commit(TransactionHelper.java:94)
... 30 more
Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 33 seconds
BEA1-460E808DE23C779E385F
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1734)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1607)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1879)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1517)
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:516)
... 2 more1. Is there any way to override this transaction timeout at the service or data space level?
You can set trans-timeout-seconds in the weblogic-ejb-jar.xml for your dataspace. You'll find it in <dataspaceName>dspejb.jar in <domain>/dsp/dataSpaces/<dataspaceName>request_handlers.ear. I've include a complete weblogic-ejb-jar.xml (at the end of the post) so you can see where to add it. Just copy-paste the <transaction-descriptor>...</>
the request handlers ear is created when the dataspace is deployed the first time and during a full-deploy (i.e. you don't have to go back and edit it after incremental deploys)
2a. Is there any more efficient way to do this update?
If you described it in painful detail, we might be able to think of something. You might find mutators helpful - http://download.oracle.com/docs/cd/E13167_01/aldsp/docs32/dsp32wiki/Mutators%20for%20Updates.html
3. If I have to break up my save operation into chunks, is there any way to effectively achieve transactional update via multiple web service calls?
You could write/host your own webservice on the ODSI server which would call ODSI via the java api. Your ws would expose operations to the following calls from your client
contextId = myWsStartUserTransaction()
while( moreChunks)
myWsUpdate(contextId, chunk)
myWSEndUserTransaction(contextId)
Just a heads-up, WLS has an anti-denial-of-service attack setting that rejects input messages over a certain size. I believe the default is 10MB. You can set it in the WLS console.
- Mike
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN'
'http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>Server</ejb-name>
<stateless-session-descriptor>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
<stateless-bean-load-algorithm>round-robin</stateless-bean-load-algorithm>
<!-- random | round-robin | weight-based -->
<!--
<stateless-bean-call-router-class-name>beanRouter</stateless-bean-call-router-
class-name> -->
<stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempo
tent>
</stateless-clustering>
</stateless-session-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>com.bea.ld.apps.dataservicesapp.server</jndi-name>
<local-jndi-name>com.bea.ld.apps.dataservicesapp.localserver</local-jndi-name>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>ServerTxRequired</ejb-name>
<stateless-session-descriptor>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
<stateless-bean-load-algorithm>round-robin</stateless-bean-load-algorithm>
<!-- random | round-robin | weight-based -->
<!--
<stateless-bean-call-router-class-name>beanRouter</stateless-bean-call-router-
class-name> -->
<stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempo
tent>
</stateless-clustering>
</stateless-session-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>com.bea.ld.apps.dataservicesapp.serverTxRequired</jndi-name>
<local-jndi-name>com.bea.ld.apps.dataservicesapp.localserverTxRequired</local-
jndi-name>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>Metadata</ejb-name>
<stateless-session-descriptor>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
<stateless-bean-load-algorithm>round-robin</stateless-bean-load-algorithm>
<!-- random | round-robin | weight-based -->
<!--
<stateless-bean-call-router-class-name>beanRouter</stateless-bean-call-router-
class-name> -->
<stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempo
tent>
</stateless-clustering>
</stateless-session-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>com.bea.ld.apps.dataservicesapp.metadata</jndi-name>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar> -
The transaction is no longer active - Transaction timed out after 30 second
We have an intermittent error here, and I'm a rookie. The error results in a 500 being sent to the customer every 10th-20th POST and only occurs under heavy load. The heavy loading is over the for the day, but it'll be back.
My first suspicion was the app code doing transaction work and having database performance problems. But the app is non-transactional and the database is fine. The server farm nodes (4) are all experiencing the problems at equal rates, and the other apps on the farm are fine, so it appears to be app-specific rather than rooted in server state or database state.
I looked at the stack a little more closely and it appears to be some kind of internal persistence issue, but a completely foreign one to me. We have no Persistent Stores configured, so I don't know where to even start on this puppy.
EJB Exception occurred during invocation from home: weblogic.ejb.container.internal.StatelessEJBLocalHomeImpl@d1e1f4 threw exception: <1.0.0 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
<1.0.0 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:3784)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:97)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:83)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:59)
at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.handleCheckedException(SelectResultObjectProvider.java:155)
at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:40)
at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1219)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:987)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:839)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:770)
at kodo.kernel.KodoQuery.execute(KodoQuery.java:47)
at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:525)
at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:229)
at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:269)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactionsExcludingApplication(ApproveApplicationHelper.java:167)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactions(ApproveApplicationHelper.java:129)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.stageAction(ApproveApplicationHelper.java:74)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean.performAction(ApproveApplicationSessionBean.java:348)
at sun.reflect.GeneratedMethodAccessor2150.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at weblogic.ejb.container.injection.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:68)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
at $Proxy365.performAction(Unknown Source)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.performAction(ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.java:148)
at com.company.buapp.si.ApplicationWS.performAction(ApplicationWS.java:114)
at sun.reflect.GeneratedMethodAccessor2149.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:50)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:42)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:247)
at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97)
at weblogic.wsee.jaxws.MonitoringPipe.process(MonitoringPipe.java:98)
at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62)
at com.sun.xml.ws.server.WSEndpointImpl$1.process(WSEndpointImpl.java:139)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:153)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:235)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:36)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:178)
at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:188)
at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:57)
at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImpl.next(Unknown Source)
at org.apache.openjpa.lib.jdbc.DelegatingResultSet.next(DelegatingResultSet.java:106)
at org.apache.openjpa.jdbc.sql.ResultSetResult.nextInternal(ResultSetResult.java:210)
at org.apache.openjpa.jdbc.sql.SelectImpl$SelectResult.nextInternal(SelectImpl.java:2209)
at org.apache.openjpa.jdbc.sql.AbstractResult.next(AbstractResult.java:168)
at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.next(SelectResultObjectProvider.java:99)
at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:35)
at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1219)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:987)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:839)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:770)
at kodo.kernel.KodoQuery.execute(KodoQuery.java:47)
at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:525)
at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:229)
at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:269)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactionsExcludingApplication(ApproveApplicationHelper.java:167)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactions(ApproveApplicationHelper.java:129)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.stageAction(ApproveApplicationHelper.java:74)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean.performAction(ApproveApplicationSessionBean.java:348)
at sun.reflect.GeneratedMethodAccessor2150.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at weblogic.ejb.container.injection.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:68)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
at $Proxy365.performAction(Unknown Source)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.performAction(ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.java:148)
at com.company.buapp.si.ApplicationWS.performAction(ApplicationWS.java:114)
at sun.reflect.GeneratedMethodAccessor2149.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:50)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:42)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:247)
at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97)
at weblogic.wsee.jaxws.MonitoringPipe.process(MonitoringPipe.java:98)
at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62)
at com.sun.xml.ws.server.WSEndpointImpl$1.process(WSEndpointImpl.java:139)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:153)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:235)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:36)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)This was actually my first conclusion as well. But when I went to the Data Source for this connection, I found it's a non-transactional driver. That's what made me go back and give the trace a second look. I don't see any references to the Data Source in question. It's OpenJPA stuff and Session persistence stuff.Non-XA drivers can still participate in an XA transaction via a variety of JDBC data source options - for example, labeled "1PC" and "LLR" on the console. (If you want to understand the particulars search for "JTS" or "LLR" in the JDBC edocs).
You seem to be suggesting maybe the setting can be made in a config doc, possibly of the app itself, right? Right. EJBs have a transaction-timeout attribute.
As opposed to setting it in the console. WebLogic has a domain wide default transaction-timeout setting that can be set on the console, but I tend not to recommend using it. In addition, there's something called a "deployment plan" which can be used to override some of the common EJB attributes via configuration, but I'm not personally familiar with its usage.
But isn't the setting vapor if we're using a nonXA driver?No.
I wonder if this thing couldn't be telling me it's waiting on the persistence subsystem to come available to store simple session data? Sometimes the problem is that there are periodic app requests that are more complex/larger than others. Sometimes the system is simply overloaded, and takes 30 seconds to honor a request that might normally take 10 seconds.
That other app is all about persistence. What if app2 is sucking some persistence subsystem dry and app 1 is waiting just to store session data? Could be.
If the nonXA thing really does kill the quick timeout workaround, how could I health-check the persistence subsystem?Don't know. At a wild guess I'd check for CPU's at 100% on all involved serves, and examine database stats. -
Transaction timed out with oracle 9i
Hi,
I am working with weblogic6.1.
Sometimes (very seldom) I have a problem which I don't undserstand.
The transaction stops and and after some time I get TimedOutException.
This time it happend in the findByPrimaryKey of a CMP Entity bean.
I have this problem only with Oracle 9i. with oracle8i everything works
fine.
I'm using oracle thin driver (I put oracle12.zip at the begin of weblogic
classpath)
Is this problem of oracle?
Does WLS 6.1 support Oracle9i?
Thanks for any hints
Szymon
stack trace:
javax.ejb.FinderException: Problem in findByPrimaryKey while preparing or
execut
ing statement: 'weblogic.jdbc.rmi.SerialPreparedStatement@197155':
java.sql.SQLException: The transaction is no longer active (status = Marked
roll
back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction
timed
out after 561 seconds
Xid=21550:aea95ccd7f28edb9(4655671),Status=Active,numRepliesOwedMe=0,numRepl
iesO
wedOthers=0,seconds since begin=561,seconds
left=30,activeThread=Thread[ExecuteT
hread: '14' for queue: 'default',5,Thread Group for Queue:
'default'],ServerReso
urceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[
mydo
main+myserver]=(state=active),properties=({weblogic.jdbc=t3://172.16.0.28:70
01})
,OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorUR
L=my
server+172.16.0.28:7001+mydomain+,
Resources={})],CoordinatorURL=myserver+172.16
.0.28:7001+mydomain+)]). No further JDBC access is allowed within this
transact
ion.
java.sql.SQLException: The transaction is no longer active (status = Marked
roll
back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction
timed
out after 561 seconds
Xid=21550:aea95ccd7f28edb9(4655671),Status=Active,numRepliesOwedMe=0,numRepl
iesO
wedOthers=0,seconds since begin=561,seconds
left=30,activeThread=Thread[ExecuteT
hread: '14' for queue: 'default',5,Thread Group for Queue:
'default'],ServerReso
urceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[
mydo
main+myserver]=(state=active),properties=({weblogic.jdbc=t3://172.16.0.28:70
01})
,OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorUR
L=my
server+172.16.0.28:7001+mydomain+,
Resources={})],CoordinatorURL=myserver+172.16
.0.28:7001+mydomain+)]). No further JDBC access is allowed within this
transact
ion.
at
weblogic.jdbc.jts.Connection.checkIfRolledBack(Connection.java:498)
at weblogic.jdbc.jts.Statement.setInt(Statement.java:606)
at
weblogic.jdbc.rmi.internal.PreparedStatementImpl.setInt(PreparedState
mentImpl.java:104)
at
weblogic.jdbc.rmi.SerialPreparedStatement.setInt(SerialPreparedStatem
ent.java:137)
at
com.verdisoft.datasource.ejb.contact.Person_vjvtzf__WebLogic_CMP_RDBM
S.ejbFindByPrimaryKey(Person_vjvtzf__WebLogic_CMP_RDBMS.java:1531)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.findByPrimaryKey(RDB
MSPersistenceManager.java:171)
at
weblogic.ejb20.manager.BaseEntityManager.findByPrimaryKey(BaseEntityM
anager.java:435)
at
weblogic.ejb20.manager.BaseEntityManager.localFindByPrimaryKey(BaseEn
tityManager.java:389)
at
weblogic.ejb20.internal.EntityEJBLocalHome.findByPrimaryKey(EntityEJB
LocalHome.java:266)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
findByPrimaryKey(PersonBean_vjvtzf_LocalHomeImpl.java:144)
at
com.verdisoft.datasource.ejb.contact.PersonBean.ejbHomeGetByKey(Perso
nBean.java:504)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
getByKey(PersonBean_vjvtzf_LocalHomeImpl.java:297)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.getBeanAdapter(EJBAdapter
Bean.java:872)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItemInternal(EJBAda
pterBean.java:834)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItem(EJBAdapterBean
.java:808)
at
com.verdisoft.datasource.ejb.EJBAdapterBean_s83q9a_EOImpl.updateItem(
EJBAdapterBean_s83q9a_EOImpl.java:146)
at
com.verdisoft.datasource.DataAdapterManagerBean.updateItem(DataAdapte
rManagerBean.java:144)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl.updateI
tem(DataAdapterManagerBean_plajw8_EOImpl.java:614)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl_WLSkel.
invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:282)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:97)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:231)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:144)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
at
com.verdisoft.datasource.ejb.contact.Person_vjvtzf__WebLogic_CMP_RDBM
S.ejbFindByPrimaryKey(Person_vjvtzf__WebLogic_CMP_RDBMS.java:1715)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.findByPrimaryKey(RDB
MSPersistenceManager.java:171)
at
weblogic.ejb20.manager.BaseEntityManager.findByPrimaryKey(BaseEntityM
anager.java:435)
at
weblogic.ejb20.manager.BaseEntityManager.localFindByPrimaryKey(BaseEn
tityManager.java:389)
at
weblogic.ejb20.internal.EntityEJBLocalHome.findByPrimaryKey(EntityEJB
LocalHome.java:266)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
findByPrimaryKey(PersonBean_vjvtzf_LocalHomeImpl.java:144)
at
com.verdisoft.datasource.ejb.contact.PersonBean.ejbHomeGetByKey(Perso
nBean.java:504)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
getByKey(PersonBean_vjvtzf_LocalHomeImpl.java:297)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.getBeanAdapter(EJBAdapter
Bean.java:872)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItemInternal(EJBAda
pterBean.java:834)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItem(EJBAdapterBean
.java:808)
at
com.verdisoft.datasource.ejb.EJBAdapterBean_s83q9a_EOImpl.updateItem(
EJBAdapterBean_s83q9a_EOImpl.java:146)
at
com.verdisoft.datasource.DataAdapterManagerBean.updateItem(DataAdapte
rManagerBean.java:144)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl.updateI
tem(DataAdapterManagerBean_plajw8_EOImpl.java:614)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl_WLSkel.
invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:282)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:97)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:231)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:144)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
com.verdisoft.datasource.exception.DataNotFoundException: Object not found:
data
source://private_addressbook/ejbcontact/john1025100151518/12770
at
com.verdisoft.datasource.ejb.EJBAdapterBean.getBeanAdapter(EJBAdapter
Bean.java:876)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItemInternal(EJBAda
pterBean.java:834)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItem(EJBAdapterBean
.java:808)
at
com.verdisoft.datasource.ejb.EJBAdapterBean_s83q9a_EOImpl.updateItem(
EJBAdapterBean_s83q9a_EOImpl.java:146)
at
com.verdisoft.datasource.DataAdapterManagerBean.updateItem(DataAdapte
rManagerBean.java:144)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl.updateI
tem(DataAdapterManagerBean_plajw8_EOImpl.java:614)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl_WLSkel.
invoke(Unknown Source)Irene Ho wrote:
Dear all,
When the java application program tries to insert the data (around 300
records). Sometimes, the error occurs as "EJB Exception:
weblogic.transaction.internal.TimedOutException: Transaction timed out after
95 seconds".
When the error occurred, only one java application was running. Furthermore,
I set the JTA-->Timeout Seconds to 30 in the thr the Weblogic console. The
configuration of the server is WebLogic 7.0 with SP2 and Oracle 8.1.7.
Anyone know what happen and how to resolve the problem? The error is due to
the entity bean, Weblogic or Oracle?
Thanks a lot.
IreneOr configuration. You can set your timeout to a different value. It is likely
to be an oracle problem. We don't do anything unnecessary to delay your application
code. You may be able to check the jdbc log or jta log to see when the tx starts and
how long it takes to progress. If you note a delay, you could take a server
thread dump to see what weblogic is doing. Typically it will be waiting for
Oracle to respond from a jdbc call.
Joe
Maybe you are looking for
-
Call function moduel in STARTIG NEW TASK
Hi All, I am calling a custom function module using " <b>starting new task</b> call function 'Y_CT_EVENT_TRIGGER' starting new task yscchdr-docno exporting event = v_event objtype = c_yct ntime = v_ntime tables
-
Setting monitor resolution in the login manager, before session launch
Hey guys, I want to have SLiM set the resolution to "auto" once it boots. At the moment, it seems like it boots directly into 800x600, and not into my native resolution, 1366x768. Sometimes I have an external monitor connected as well, and it's a goo
-
Can't Access Desktop & Screen Saver Preferences
Hi everyone, Can't figure this one out!!! In the main System Preferences>Show All, the title of Desktop & Screen Saver icon has changed to "DesktopScreenEffectsPrefDock". It is all smashed together like that and partially overlays the "Appearance" ti
-
How do you change an icons desktop picture?
Anybody know how to change the picture of a folder? I dont like the standard blue folders all over my desktop
-
Multiple AP541N dropping clients
I have 3 AP541Ns setup in a small environment. The wireless clients use laptops to attach, via RDP, to a Microsoft Terminal Server. They need the ability to walk, with laptop, from room to room, IE roaming wireless clients. The issue is the client