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

Similar Messages

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.

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.

JDBC activity timed out while updating a table.

Hi,
We have observed the exception *'JDBC activity timed out while updating the table -Table1"* in our logs in prod environment.
1)we verified the AWR report for that particular time and observed that one update statement was trying to update the table table1.
its a simple update statement as below
UPADTE TABLE1 SET COL1=VAL1,COL2=VAL2 WHERE ID1=VAL1 AND ID2=VAL2;
there is a PK index on ID2 column.
2)we also came to know that there were no locks on TABLE1 during this time.
can some one please let me know what could be the possible reason for this kind of exception?
Thanks

958572 wrote:
Hi,
We have observed the exception *'JDBC activity timed out while updating the table -Table1"* in our logs in prod environment.
1)we verified the AWR report for that particular time and observed that one update statement was trying to update the table table1.
its a simple update statement as below
UPADTE TABLE1 SET COL1=VAL1,COL2=VAL2 WHERE ID1=VAL1 AND ID2=VAL2;
there is a PK index on ID2 column.
2)we also came to know that there were no locks on TABLE1 during this time.
can some one please let me know what could be the possible reason for this kind of exception?
ThanksOS/Networking mis-configuration.
Oracle does not know or care about the type or flavor of remote client (JDBC, OCI, ODBC, etc).
Oracle's default configuration contains no timeout.
I suspect a FireWall setting.

"timed out while receiving the initial server greeting" mail stalled why?

"relay=none, delay=2473, delays=1880/593/0/0.01, dsn=4.4.2, status=deferred (delivery temporarily suspended: conversation with 127.0.0.1[127.0.0.1] timed out while receiving the initial server greeting)"
server stalling mail in queue
perl5.10.0 amavsid running in Activity Monitor at 100%
haven't changed anything, just started today.
Any suggestions?

postfix and amavis might be out of sync.
open terminal
tail -f /var/log/mail.log
watch your log, postfix will report what the trouble is, don't snip the log,
serveradmin stop mail
postqueue -p
postsuper -r ALL
serveradmn start mail
watch your log. also make sure your firewall is not doing anything goofey with 127.0.0.1
if the server has been running for a log time,.. some programs leak. eventually you have to kick services at least.

I am getting an error message that my network connection has timed out. while trying to update my iPhone on iTunes. Has anyone found a solution? I was given some advice about turning off my firewall and/or virus protection but am nervous about doing that.

I get a message that my network connection has timed out while trying to update my iPhone on iTunes. Has anyone else had that problem and if so what solutions have you found? I was told to turn off my firewall and/or virus protection while updating but am nervous about doing that for obvious reasons. I'm also disgusted with Apple not providing free tech support.

See this article about the ports that have to be open during the update process. iTunes has to contact Apple during the download. iTunes for Windows: Troubleshooting security software issues

Request timed out while waiting for response!!

Hi All,
My scenario is PROXY to SOAP. I am getting below error while posting to WEBSERVICE.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<ns1:stackTrace xmlns:ns1="http://xml.apache.org/axis/">Failed to deliver inbound WS message, code=503 and reason=Request timed out while waiting for response. at com.sonicsw.net.http.ws.WSHttpProtocolHandler$HttpInBrokerHandler.invoke(WSHttpProtocolHandler.java:833) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453) at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.sendToSOAPStack(WSHttpProtocolHandler.java:630) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.dispatch(WSHttpProtocolHandler.java:537) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.servicePost(WSHttpProtocolHandler.java:284) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.service(WSHttpProtocolHandler.java:609) at com.sonicsw.net.http.HttpProtocolHandler.handle(HttpProtocolHandler.java:471) at progress.message.net.http.server.HttpConnectionHandler.handle(HttpConnectionHandler.java:170) at progress.message.net.https.server.SonicHttpsConnection.service(SonicHttpsConnection.java:156) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831) at progress.message.net.https.server.SonicHttpsServer.handleConnection(SonicHttpsServer.java:449) at progress.message.net.https.server.SonicHttpsServer.handle(SonicHttpsServer.java:364) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)</ns1:stackTrace>
Any Idea ? Do I need to change anything in my SOAP Channel or BAsis should change the Time Parameter?
Thanks,
Pushkar Patel

Hi,
>>>>>>>Request timed out while waiting for response.
See the below link, it might be helpful to you for timed out issue.
[Link1|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?quicklink=index&overridelayout=true]
Regards,
Rajesh

Getting session has timed out while trying to redeem a gift card. have had no problem in the past. am running a g4 since 2002 with os 10.4 and itunes 9. have no internet problems and can connect to store ok. so far apple no help keeps blaming it on othrs

am having trouble for the first time trying to redeem a gift card. Everything same on computer, OS, and internet connection. have been able to redeem other cards. this time am getting "SESSION HAS TIMED OUT" while trying to redeem card. have contacted apple and checked out all their suggestion iE:( must be your connection. typed in code wrong, too old version of itunes, etc) anything but why would a gift card code bee tied to a specific vetrsion of ITUNES. Rediculous!! there has to be others out there that have an older version if itune than i have. has anyone ever had the error "SESSION HAS TIMED OUT" and if so was it corrected?? any information other than apples {change password and give us lots of personal info they probably have) would be appreciated..

Hello,
As far as I can see, that Verizon Jet Pack wireless Modem uses WPA2 to connect.
The Router might complicate things right now.
Make a New Location, Using network locations in Mac OS X ...
http://support.apple.com/kb/HT2712
Is that Interface dragged to the top of Network>Show:>Network Port Configurations and checked ON?
The Interface that connects to the Internet, needs to be drug to the top of System Preferences>Network>Show:>Network Port Configurations and checked ON.
If using Wifi/Airport...
Instead of joining your Network from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed.

The operation timed out while writing (kCFStreamStatusOpening)

iMessage cant send files. This is what it says in the file transfer window. "the operation timed out while writing (kCFStreamStatusOpening)" Help

Hi,
In the past in the Mountain Lion (Messages 7.x.x) I have sent quite large photos via the iMessages account of several GBs of data.
I have yet to do the same in Messages 8 (Mavericks) but don't expect for this to have changed.
I do know that the Messages 8 app tends to zip some files before sending when dragged from other apps such as a Browser or iPhoto.
I have sent a Keynote file to my iPhone in Messages 7.x.x but this was only 334 kb
What sort of files are you trying to send ?
If not zipped already it may pay to try this first.
7:21 pm Sunday; November 3, 2013
 iMac 2.5Ghz 5i 2011 (Mavericks 10.9)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad

HT1688 the network connection timed out while updating iphone software

the network connection timed out while updating iphone software and cannot continue.

Might want to search the Mac forum or post there... also, this thread is over 2 years old.

MAX timed out while waiting for a driver

I am getting an error when starting MAX. the error is that MAX timed out while waiting for a driver (nidaqe plug-in). I have a PCI-GPIB card and an PCI-MXI-2 card in the PC. The operating system is Windows XP.
I am able to see both these cards under the Windows Device Manager>Hardware.
MAX version is 4.6.1f0
I have also installed NI-488.2 and NIVXI331 driver installed on the computer.
Any help will be appreciated.
Thank you.
vxiguy

Hi vxi_guy,
What you're seeing could be the result of a few different things. First, I would check to see if the NI Configuration Manger and NI Device Loader are running, as per this KB. Then, if that doesn't work, I would explore the solutions described in this KB. Please let me know if neither of those articles resolve the issue. Have a good one!
aNItaB
Applications Engineer
National Instruments
Digital Multimeters

Client Timed Out While Answering Challenge HELP please!

ok, so i just added a WPA password to our airport extreem so my neighbor would stop using it. this worked, and for a second it seemed to be running good. now though when im on using bootcamp, running counter strike every time i try to join a server this error message comes up "Client Timed Out While Answering Challenge", and i have no clue why and its really ticking me off. The internet works fine on the windows side, and counter strike worked ok before i set the WPA passoword except real slow because of my neighbor using it. but no this error message is very annoying and if anyone knows how to get rid of it please help.

Close itunes then
Check your internet settings.
Control Panel – Internet Options – Advanced
Check SSL 3.0 and TLS 1.0
Uncheck “Check for server certificate revocation (requires restart)”
Click Apply
Click Okay
Open itunes and try again

Qmaster error: shared storage client timed out while subscribing to...

Here's my Qmaster setup:
computer 1: CONTROLLER, no nodes
- 8TB RAID hooked up via Fiber
- connected to the GigE network switch via a 6-port bond
- cluster storage set to a path on the RAID
computers 2, 3, 4, 5: RENDER NODES
- each computer has a 2-port bonded connection with the GigE switch
computer 6: Client, with FCS2 installed.
- connected with a single GigE link
I have set up this cluster primarily for command-line renders, and it works great. I submit command-line renders from the client computer, which get distributed and executed on each node. The command line renders specify a source file on the RAID, and a destination path on the RAID. Everything works great.
I run into trouble when trying to use Compressor with this same setup. The files are on the RAID, and all my computers have an NFS automount that puts it in the /Volumes folder on each computer.
I set up my Compressor job and submit it to the cluster. It submits sucessfully, and distributes the work. After a few seconds, each node gives me a timeout error:
"Shared storage client timed out while subscribing to [computer1.local/path to cluster storage]"
Is this a bandwidth issue? Command line renders work fine, I can render 16 simultaneous Quicktimes to the RAID over NFS. I don't see much network activity on any of the computers when it's trying to start the Compressor render, it's as if it's not even trying to connect.
If I submit the SAME compressor job to a cluster with nodes ONLY on the controller computer, it renders fine. Clearly the networked nodes are having trouble connecting to the share for some reason.
Does anybody have any ideas? I have tried almost everything to get this to work. Hooking up each node locally to the RAID is NOT an option unfortunately.

WELL I DO NOW!
Thanks. it's taken 6th months and several paid 'professionals' and then you come in here...swinging your minimalist genius. one line. one single line. and its done.
if you are in london, lets lift a beer or five together.
thank you sir. thankyou!

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

Javax.transaction.SystemException: Timed out while in 'Logging' state!!!!

Similar Messages

Maybe you are looking for