Javax.transaction.SystemException: Exceeded maximum allowed transactions on

Hi,
I receive the following error when restarting weblogic server instance. Same error occurs when re-deploying the package.
I had previously deployed this package OK. Nothing has changed for the jar file it is complaining about.
I have restarted all java processes and even had the unix server restarted, however the same error comes up. I have no idea what to do.
Currently I have no application deployed as it fails every time. Nobody I know has seen this error or knows how to recover.
Please help!
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application NBAPP_1_10_2B on nbste_cluster.: weblogic.management.DeploymentException:
<b>Exception:weblogic.management.ApplicationException: activate failed for mca-ejbs.jar
Module: mca-ejbs.jar Error: Exception activating module: EJBModule(mca-ejbs.jar,status=PREPARED)
Unable to deploy EJB: eontec.bankframe.TransactionMetaData from mca-ejbs.jar:
[EJB:011007]Unable to create EJB Persistence Manager.
javax.transaction.SystemException: Exceeded maximum allowed transactions on server 'nbste_app1b_1'</b>
at weblogic.transaction.internal.ServerTransactionManagerImpl.createTransaction(ServerTransactionManagerImpl.java:1395)
at weblogic.transaction.internal.TransactionManagerImpl.internalBegin(TransactionManagerImpl.java:248)
at weblogic.transaction.internal.ServerTransactionManagerImpl.internalBegin(ServerTransactionManagerImpl.java:303)
at weblogic.transaction.internal.ServerTransactionManagerImpl.begin(ServerTransactionManagerImpl.java:259)
at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:248)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:210)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
at weblogic.ejb20.manager.ROManager.setup(ROManager.java:109)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1057)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1362)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:631)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3274)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2173)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2434)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2352)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2136)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:676)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application NBAPP_1_10_2B on nbste_cluster.: weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: activate failed for mca-ejbs.jar
Module: mca-ejbs.jar Error: Exception activating module: EJBModule(mca-ejbs.jar,status=PREPARED)
Unable to deploy EJB: eontec.bankframe.TransactionMetaData from mca-ejbs.jar:
[EJB:011007]Unable to create EJB Persistence Manager.
javax.transaction.SystemException: Exceeded maximum allowed transactions on server 'nbste_app1b_2'
at weblogic.transaction.internal.ServerTransactionManagerImpl.createTransaction(ServerTransactionManagerImpl.java:1395)
at weblogic.transaction.internal.TransactionManagerImpl.internalBegin(TransactionManagerImpl.java:248)
at weblogic.transaction.internal.ServerTransactionManagerImpl.internalBegin(ServerTransactionManagerImpl.java:303)
at weblogic.transaction.internal.ServerTransactionManagerImpl.begin(ServerTransactionManagerImpl.java:259)
at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:248)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:210)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
at weblogic.ejb20.manager.ROManager.setup(ROManager.java:109)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1057)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1362)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:631)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3274)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2173)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2434)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2352)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2136)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:676)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)<pre></pre><pre></pre>

Hi All,
I am facing similar problem whne I try to deploy my Web part of the Application. I have JAR'ed the EJB's and that seems to get deployed properly only the web part is not getting loaded.
The following is the error message:
Exception:weblogic.management.ApplicationException: prepare failed for myWebApp
Module: annaweb Error: Could not load myWebApp: java.lang.NullPointerException
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2467)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for myWebApp
Module: annaweb Error: Could not load myWebApp: java.lang.NullPointerException
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Have anyone faced similar problems, please let me know about the solution or suggestions.
Thanks in Advance.
- Jayashree
Edited by jayashree_kumar at 01/17/2007 10:09 AM

Similar Messages

Column name length exceeds maximum allowed

Hello,
I get this error when am trying to create a table. ERROR: Column name length exceeds maximum allowed length(30).
Is it able to extend this length to be more than 30 ? By the way I am using Oracle 11g
Regards,
Moussa El Tayeb
about.me/MoussaEltayeb

Hello,
also Oracle has some limits. For more Information see the logical limits
http://docs.oracle.com/cd/E14072_01/server.112/e10820/limits.htm
regards
Peter

Upgrade error "exceeded maximum allowed length (134217728 bytes)

Hi:
I'm trying to add a patch to the OEM patch cache, and I'm getting an error:
Error: - Failed to Upload File.Uploaded file of length 545451768 bytes exceeded maximum allowed length (134217728 bytes)
The patch file is what it is (545451768 bytes). How do I install this patch? I'm trying to upgrade a 10.1.0.3 DB to 10.1.0.4
Thanks

This log is for external user.
Did you deploy Lync edge server?
The Edge Server rejects the authentication request, and redirects the Lync 2010 client to the Lync Web Services (https://lyncexternal.contoso.com/CertProv/CertProvisioningService.svc).
It seems the redirect fails, please check the event view on Lync edge Server.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Index Name Exceeds Maximum Allowed

I'm using the IKM Oracle Incremental Update and it creates a unique index on my interface table. The problem is that the interface table is i$_<Table Name>. The index is then created as i$_<Table Name>_idx. The table I am working with is already 25 characters and the maximum allowed on Oracle (10g) is 30. Is there a setting that I need to change or do I have to customize the knowledge module?
Thank you,
Troy

So you can try to remove a few char without changing a lot of thing.
For exemple you can modifiy the Unique Index procedure of your IKM Oracle Incremental Update.
I think you have this in the Index procedure:
create unique index <%=snpRef.getTable("L","INT_NAME","W")%>_idx on <%=snpRef.getTable("L","INT_NAME","W")%> (<%=snpRef.getColList("", "[COL_NAME]", ",", "", "(UK)")%>)
<%=snpRef.getUserExit("FLOW_TABLE_OPTIONS")%>
Which return you the the name of your index like i$_<Table Name>_idx
if you change what is in bold in the script you can remove 5 char and maybe it woulb be good for you.
By replacing INT_NAME by TARG_NAME you can obtain an index nammed <Table Name>_idx which remove 3 char
and after that you can change the "_idx" by "IX" which will give you <Table Name>IX and which remove 2 more char
so the procedure will look like :
create unique index <%=snpRef.getTable("L","TARG_NAME","W")%>ID on <%=snpRef.getTable("L","INT_NAME","W")%> (<%=snpRef.getColList("", "[COL_NAME]", ",", "", "(UK)")%>)
<%=snpRef.getUserExit("FLOW_TABLE_OPTIONS")%>
--> Evidently you can change a lot of other things to obtain less char for the name of your index

"Project exceeds maximum allowed content duration" in iDVD

Trying to burn in iDVD 4.0.1, two and a half hours of video captured in FCE4. Size of file: 31.8 GB.
Got the above error. I was able to burn a one and one half hour capture, size 20 GB.
These are the original QuickTime Movie files produced by Capture. I did not Export.
Anyone know what iDVD's max content duration is? Is it a time max or a file size max?
Would exporting compress the file such that I could get more minutes of video on one DVD?
To try to answer that, I then did File/Export on the 2.5 hour QTMovie file, yielding a 1.62 GB FCEMovie file, still 2.5 hours. I tried to burn DVD but got the same error message - exceeds max allowed content duration.
Thoughts on max duration? Rental movies go longer than 2.5 hours, right?
Thanks,
TT

hey there TTTTTT,
iDVD has time limits--2 hours on a single-layer DVD, 4 hours on a dual-layer. commercial DVDs may employ a dual layer disc to get more that 2 hours on a disc or use other options for getting more info on a disc--reducing the bit rate for the audio, using variable compression on the video, etc... commercial discs are usually replicated from tapes(DLT) & maybe authored using hardware accelerated very, very expensive software. if your Mac has the capability, try using a dual-layer disc. you can find this info this way: click the Apple> About This Mac> More Info> System Profile> Disc Burning.
good luck.

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 AM

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 AM

Javax.transaction.SystemException: Timeout during commit processing

          In my Workshop 8.1 SP2 project I have a Custom Java Control whose methods I call
          from my JPF. From that custom control I create a remote connection to a Weblogic
          6.1 Application server. I execute remote methods and get the expected objects
          back with no problem. The problem is that I cannot return that object from my
          custom control back to my jpf. As soon as the method's return statement is executed,
          the process hangs for a considerable period of time and then throws the following
          Exception:
          An error has occurred:
          Exception while commiting Tx : Name=[EJB com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)],Xid=BEA1-0005BF0F3E6E72419698(655489),Status=Unknown,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
          since begin=217,seconds left=42983,XAServerResourceInfo[BMResourceManager]=(ServerResourceInfo[BMResourceManager]=(state=new,assigned=none),xar=null),SCInfo[midway+cgServer]=(state=active),SCInfo[prdsdomain+prdsserver]=(state=active),properties=({weblogic.transaction.name=[EJB
          com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=cgServer+172.23.83.174:7001+midway+t3+,
          XAResources={},NonXAResources={})],CoordinatorURL=prdsserver+172.23.4.109:7041+prdsdomain+t3+);
          nested exception is:
          javax.transaction.SystemException: Timeout during commit processing
          Start server side stack trace:
          javax.transaction.SystemException: Timeout during commit processing
          at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:243)
          at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.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:305)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          caused by: : javax.transaction.SystemException: Timeout during commit processing
          Start server side stack trace:
          javax.transaction.SystemException: Timeout during commit processing
          at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:243)
          at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.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:305)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          As soon as I take out RMI calls from my custom control's code, I can return any
          object I want back to my JPF. Here is the what I am thinking is happenning.
          The system that runs on Weblogic 6.1 manages its own transactions and begins a
          new transaction every time a session bean residing on that server is invoked.
          In addition, Weblogic 8.1 starts an internal transaction when the Custom Java
          Control makes a call. Could there be some kind conflict? If yes, is it possible
          to disable transactions from the Java Control?
          Thank you very much
          Alex Mayzlin


Horst,
          "aa aa" <[email protected]> wrote in message news:20701457.1093414960276.JavaMail.root@jserv5...
          > we are getting the same Exception. As nobody replied to your question, it would be interesting, if you found any solution
          yourself?
          >
          > Additional info:
          > We are also getting these error messages from BEA when testing connections in pool before and after the exception:
          >
          > <20.08.2004 19.32 Uhr CEST> <Error> <JDBC> <BEA-001112> <Test "SELECT count(*) FROM invoice" set up for pool "ABCConnection Pool"
          failed with exception: "java.sql.SQLException: ORA-01591: lock held by in-doubt distributed transaction 4.47.141655".>
          Generally it's a good idea to use Oracle's system DUAL table
          for testing connections on reserve. Try to change your ABCConnection
          connection pool configuration to use DUAL as the test table
          instead of "invoice".
          Regards,
          Slava Imeshev

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.

Java.transaction.SystemException

How to replicate the below exceptions:
1. java.transaction.SystemException
2. javax.transaction.xa.XAException
Thanks in advance,
Jagan

How to replicate the below exceptions:
1. java.transaction.SystemException
2. javax.transaction.xa.XAException
Thanks in advance,
Jagan

Unit of measure EA allows transactions in decimals ? Is EA indivisible?

Unit of measure EA allows transactions in decimals ? Is EA indivisible?
There are two scenarios. While creating a Bill of material - based on the configuration (see below) if you enter a quantity with decimals for a part number for which the Basic UOM is EA the system displays a message "Unit of measure EA does not support decimal places" THIS IS GOOD AS EXPECTED
While transacting using MB1B, MB1C, MB1A, MFBF, MIGO or other transactions the system DOES NOT check and it is currently allowing us to post with decimals (1.25, 1.312) for part number for which the unit of measure is EA.
Was not EA supposed to be an indivisible unit of measure? why is the warning message getting activated while creating or changing a BOM and why not while transacting stock?
We have configured EA in the CUNI transaction as follows:
Int. meas. unit      EA
Commercial           EA              each
Technical            EA              each
Decimal places
float. point exp.
ISO code             EA
                                      Primary code
Numerator            1
Denominator          1
Exponent             0
Additive constant    0.000000       X Commercial meas.unit
Decimal pl. rounding                 Value-based commt
Unit of meas.family

you cannot restrict this behaviour with CUNI customizing, you can only check and stop this in a user exit.
SAP inventory managment allows and stores 3 decimals for any unit of measure. You can only define how it will show the value to the users and how it will round the decimals if it calculates the conversion. But if you enter manually with decimals, then SAP will not round this.
please read OSS Note 931971 - Decimal places in stocks and stock postings
and
Note 77525 - Quantity unit conversion in inventory management

Sum of values exceeds the allowed maximum value per service line

Hi Guys,
While creating PO wrt to contract : I get error msg : Sum of values exceeds the allowed maximum value per service line Message no. SE402. Can I change it to warning or should I bifurcate one line into two , as the value is very big. Totalling to 11 characters excluding decimal. Its like xxx,xxx,xxx.xx inr.
Regards,
SK

Hi,
For service line items, the maximum allowed limit is 999999999.99 (total 11 digits including 2 decimals) as per design. If you want more than that, you may split the service in to two line items.
The note: 1810281 - System does not issue error message SE 402 explains the logic.
Regards,
AKPT

Credit receipt exceeds Maximum amount allowed

Hello,
We were recently requested to update one of our expense type's "Default/Max. value", also we were requested to have the "Amount type" set to "Error message for exceeding maximum". We have now come across a problem where credit receipts that are uploaded to our system are above the maximum amount allowed and are receiving the error message, these receipts cannot be itemized with personal expense down to the maximum because of the error message, so the users are having to enter these receipts in manually.
Is there a way to keep the error message for the maximum value and be able to itemize the receipt even if the receipt is above the limit?
- Edward Edge

hi
no you cannot.
the only way you can change the system error message as warning and proceed.

The request exceeds the maximum allowed database size of 4 GB

I have craeted a user in oracle 10g with following commands
CRAETE USER USERNAME IDENTIFIED BY PASSWORD
DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp;
Grant create session to USERNAME;
Grant create table to USERNAME;
Grant create view to USERNAME;
Grant create trigger to USERNAME;
Grant create procedure to USERNAME;
Grant create sequence to USERNAME;
grant create synonym to USERNAME;
after that when i want to craete a table i got following error
SQL Error: ORA-00604: error occurred at recursive SQL level 1
ORA-12952: The request exceeds the maximum allowed database size of 4 GB
00604. 00000 - "error occurred at recursive SQL level %s"

Error starting at line 1 in command:
SELECT /* + RULE */ df.tablespace_name "Tablespace", df.bytes / (1024 * 1024) "Size (MB)", SUM(fs.bytes) / (1024 * 1024) "Free (MB)", Nvl(Round(SUM(fs.bytes) * 100 / df.bytes),1) "% Free", Round((df.bytes - SUM(fs.bytes)) * 100 / df.bytes) "% Used" FROM dba_free_space fs, (SELECT tablespace_name,SUM(bytes) bytes FROM dba_data_files GROUP BY tablespace_name) df WHERE fs.tablespace_name = df.tablespace_name GROUP BY df.tablespace_name,df.bytes
UNION ALL
SELECT /* + RULE */ df.tablespace_name tspace, fs.bytes / (1024 * 1024), SUM(df.bytes_free) / (1024 * 1024), Nvl(Round((SUM(fs.bytes) - df.bytes_used) * 100 / fs.bytes), 1), Round((SUM(fs.bytes) - df.bytes_free) * 100 / fs.bytes) FROM dba_temp_files fs, (SELECT tablespace_name,bytes_free,bytes_used FROM v$temp_space_header GROUP BY tablespace_name,bytes_free,bytes_used) df WHERE fs.tablespace_name = df.tablespace_name GROUP BY df.tablespace_name,fs.bytes,df.bytes_free,df.bytes_used ORDER BY 4 DESC
Error at Command Line:1 Column:319
Error report:
SQL Error: ORA-00942: table or view does not exist
00942. 00000 - "table or view does not exist"
*Cause:
*Action:

Allowed Transaction by system status in Process Orders

Hi all:
I have a problem manging the process orders, related to the system status and allowed transaction. The question is: How could I prevent the use of certains transaction (i.e. RFBU FI:Postings) when system status = TECO in one process order where status profile is not assgined (that is t003O-STSMA not filled)?.
At this moment I have a lot of process orders in that status and I want to avoid the posting from FI just if the system status = TECO
I will thank you very much for any help
Best Regards

As a standard setting, you will not be able to restrict the financial postings when an order is TECO'ed but you may do it through by enhancing user exit/ BADI in the respective transaction...

Project exceeds the maximum allowed content

Please let me know how I can correct this error message that I get when I decide to burn my DVD. (Project Duration Your project exceeds the maximum allowed content duration. You will not be able to burn your DVD).
Thank you;

Hello, Thomas,
Welcome to the discussions!
You will get the 'exceeds the maximum allowed content duration' message if your DVD project exceeds the time limit for the type of burn you have selected.
1. If your project, usually iMovie, is over 2hrs, you cannot burn it to a single layer DVD.
2. If your project is under 2hrs but your menus and submenus' audio and video content is extensive, your project will exceed the DVD capacity.
3. Most commonly, your project is over 2 hrs, but you have selected "best performance" in DVD preferences instead of "best quality." 'Best performance' is for projects that are under 60min, and 'best quality' is for those over 2 hrs. You change this in DVD preferences.
Explanation for the differences (adapted from David Pogue's little iDVD4 pamphlet):
"Choosing best performance for shorter projects allows the DVD app to allot a fixed amount of data to each frame of video, enough to make it look great no matter how many minutes of video it includes(up to 60min) so that a lot of the DVD can end up empty, but the burning process goes quickly and the video looks great.
Choosing best quality allows the DVD app to us all the space on the balnk DVD by analyzing the amount of video included and dividing it into the amount of space available on the DVD so that the amount of information used for each frame will vary from project to project, and it will take longer to burn because of the analysis time. But, it will give 2 hrs of great-looking video per disc."
Does this help??
Post back if you are still having problems, and if so, be specific in what you are trying to do and what is not working.

Javax.transaction.SystemException: Exceeded maximum allowed transactions on

Similar Messages

Maybe you are looking for