1 Reply Latest reply on Dec 21, 2006 9:36 AM by marklittle

    could not register interposed hierarchy

    qren

      I am using JBoss4.0.5.GA and JBossTS4.2.2, configured to use JTS with only one server. when I make my transaction as roll back only, I got following error, what could the problem be?

      09:29:08,281 WARN [loggerI18N] [com.arjuna.ats.internal.jts.orbspecific.interposition.resources.arjuna.generror] Server
      TopLevelAction.registerResource caught exception: org.omg.CORBA.TRANSACTION_ROLLEDBACK: Server-side Exception: vmcid:
      0xc000 minor code: 851 completed: No
      09:29:08,281 WARN [loggerI18N] [com.arjuna.ats.internal.jts.orbspecific.interposition.resources.arjuna.ipfailed] Server
      TopLevelAction - could not register interposed hierarchy!
      09:29:08,281 WARN [loggerI18N] [com.arjuna.ats.internal.jts.interposition.resources.arjuna.ipfail] Interposition.remove
      Heirarchy - could not find a3c3782:76c:4589b320:1905 to remove.
      09:29:08,281 WARN [loggerI18N] [com.arjuna.ats.internal.jts.context.genfail] ContextManager.createHierarchy caught exce
      ption: org.omg.CORBA.TRANSACTION_ROLLEDBACK: vmcid: 0x0 minor code: 0 completed: No
      09:29:08,281 ERROR [AbstractEntityManagerImpl] could not determine transaction status
      javax.transaction.SystemException
       at com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple.getTransaction(TransactionManagerImple.java:82)
       at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.getTransaction(BaseTransactionManagerDelegate.java:107)
       at org.hibernate.transaction.CMTTransaction.getTransaction(CMTTransaction.java:91)
       at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:489)
       at com.arjuna.ats.internal.jta.resources.jts.orbspecific.SynchronizationImple.before_completion(SynchronizationImple.java:128)
       at org.omg.CosTransactions.SynchronizationPOA._invoke(SynchronizationPOA.java:42)
       at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:299)
       at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:593)
       at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:735)
      09:29:08,343 WARN [loggerI18N] [com.arjuna.ats.internal.jts.orbspecific.interposition.resources.arjuna.generror] Server
      TopLevelAction.registerResource caught exception: org.omg.CORBA.TRANSACTION_ROLLEDBACK: Server-side Exception: vmcid:
      0xc000 minor code: 851 completed: No
      09:29:08,343 WARN [loggerI18N] [com.arjuna.ats.internal.jts.orbspecific.interposition.resources.arjuna.ipfailed] Server
      TopLevelAction - could not register interposed hierarchy!
      09:29:08,359 WARN [loggerI18N] [com.arjuna.ats.internal.jts.interposition.resources.arjuna.ipfail] Interposition.remove
      Heirarchy - could not find a3c3782:76c:4589b320:1905 to remove.
      09:29:08,359 WARN [loggerI18N] [com.arjuna.ats.internal.jts.context.genfail] ContextManager.createHierarchy caught exce
      ption: org.omg.CORBA.TRANSACTION_ROLLEDBACK: vmcid: 0x0 minor code: 0 completed: No
      09:29:08,375 ERROR [AbstractEntityManagerImpl] Unable to mark for rollback on PersistenceException:
      org.omg.CORBA.TRANSACTION_ROLLEDBACK: vmcid: 0x0 minor code: 0 completed: No
       at com.arjuna.ats.internal.jts.interposition.resources.arjuna.Interposition.createHierarchy(Interposition.java:186)
       at com.arjuna.ats.internal.jts.interposition.resources.arjuna.Interposition.setupHierarchy(Interposition.java:115)
       at com.arjuna.ats.internal.jts.interposition.resources.arjuna.Interposition.create(Interposition.java:74)
       at com.arjuna.ats.internal.jts.interposition.resources.arjuna.InterpositionCreator.recreateLocal(InterpositionCreator.java:48)
       at com.arjuna.ats.internal.jts.interposition.FactoryElement.recreateLocal(FactoryList.java:72)
       at com.arjuna.ats.internal.jts.interposition.FactoryList.recreateLocal(FactoryList.java:119)
       at com.arjuna.ats.internal.jts.orbspecific.TransactionFactoryImple.recreateLocal(TransactionFactoryImple.java:246)
       at com.arjuna.ats.internal.jts.context.ContextManager.createHierarchy(ContextManager.java:793)
       at com.arjuna.ats.internal.jts.context.ContextManager.currentPIContext(ContextManager.java:684)
       at com.arjuna.ats.internal.jts.context.ContextManager.current(ContextManager.java:212)
       at com.arjuna.ats.internal.jts.context.ContextManager.associate(ContextManager.java:365)
       at com.arjuna.ats.internal.jts.OTSImpleManager.current(OTSImpleManager.java:91)
       at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.getTransaction(TransactionImple.java:1135)
       at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.setRollbackOnly(BaseTransaction.java:210)
       at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.setRollbackOnly(BaseTransactionManagerDelegate.java:135)
       at org.hibernate.ejb.AbstractEntityManagerImpl.markAsRollback(AbstractEntityManagerImpl.java:432)
       at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:587)
       at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:501)
       at com.arjuna.ats.internal.jta.resources.jts.orbspecific.SynchronizationImple.before_completion(SynchronizationImple.java:128)
       at org.omg.CosTransactions.SynchronizationPOA._invoke(SynchronizationPOA.java:42)
       at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:299)
       at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:593)
       at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:735)
      09:29:08,500 WARN [loggerI18N] [com.arjuna.ats.internal.jts.orbspecific.coordinator.generror] ArjunaTransactionImple.do
      BeforeCompletion caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: vmcid: 0x0 minor code: 0 completed: No
      


        • 1. Re: could not register interposed hierarchy
          marklittle

          What could be happening here is that the parent coordinator has either rolled back, is rolling back, or has been marked for rollback_only. In which case, the subordinate coordinator cannot enlist and throws an exception. If you have created your transactions with timeouts, try increasing the timeout value.