Javax.transaction.SystemException: Timeout during commit processing

Question

          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
          

Answer 1

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