Monday, June 23, 2014

"CORBA TRANSACTION_ROLLEDBACK 0x0 No; nested exception" while loading the XMLs through batch processor in Multithreaded Environment

Below is the detailed Error while loading the XMLs through batch processor ,


CORBA TRANSACTION_ROLLEDBACK 0x0 No; nested exception is:
        org.omg.CORBA.TRANSACTION_ROLLEDBACK:
        >> SERVER (id=5def01fa, host=gbrpcr10191n02.intranet.myClient.com) TRACE START:
        >>    org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException:  ; nested exception is:
        com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction marked rollbackonly  vmcid: 0x0  minor code: 0  completed: No
        >>       at com.ibm.ejs.csi.TranStrategy.postInvoke(TranStrategy.java:254)
        >>       at com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionControlImpl.java:570)
        >>       at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:4558)
        >>       at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:4372)
        >>       at com.dwl.base.requestHandler.beans.EJSRemoteStatelessDWLServiceController_2ecdcec0.processRequest(EJSRemoteStatelessDWLServiceController_2ecdcec0.java:45)
        >>       at com.dwl.base.requestHandler.beans._EJSRemoteStatelessDWLServiceController_2ecdcec0_Tie.processRequest(_EJSRemoteStatelessDWLServiceController_2ecdcec0_Tie.java:166)
        >>       at com.dwl.base.requestHandler.beans._EJSRemoteStatelessDWLServiceController_2ecdcec0_Tie._invoke(_EJSRemoteStatelessDWLServiceController_2ecdcec0_Tie.java:106)
        >>       at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:585)
        >>       at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:461)
        >>       at com.ibm.rmi.iiop.ORB.process(ORB.java:533)
        >>       at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)
        >>       at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2915)
        >>       at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2782)
        >>       at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:65)
        >>       at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
        >>       at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1646)
        >> SERVER (id=5def01fa, host=gbrpcr10191n02.intranet.myClient.com) TRACE END.
  vmcid: 0x0  minor code: 0  completed: No,<TCRMService xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="myTCRM.xsd"><RequestControl><requestID>196</requestID><DWLControl><requesterName>SYSTEM</requesterName><requesterLanguage>100</requesterLanguage></DWLControl></RequestControl><TCRMTx>

Possible Root Cause 1 : Whenever there is a sequence of XMLs  are gets loaded through batch (through multiple submitter) and different transactions may have to update(access) same set of data in DB. There might be a case when a transaction is acquiring a lock on some data while another transaction is also waiting to fetch the same record then wait time might be reached to maximum time for transaction that is defined  . If this happens then there will be transaction rollback for some transactions and  we might be getting above mentioned errors in batch out logs.

Possible Resolution 1 : Failed transaction needs to be re-submitted through single submitter. and need to execute XMLs manually (one by one) .

P.S. there can be other possible cause of CORBA TRANSACTION_ROLLEDBACK .

No comments:

Post a Comment