0 Replies Latest reply on Oct 24, 2008 2:31 AM by Sascha Hoffmann

    Too many INSERTS?

    Sascha Hoffmann Newbie

      Hallo all. I have a question.

      I have a WebApplication where I can see, update and insert Datas.
      Furthermore I can copy a dataset and all Datas in the below Tables.

      My INSERTS are ok but after a few minutes my Application abort and I get the following error:
      [Code]
      15:29:30,093 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57ff2d:781:49007978:129 invoked while multiple threads active within it.
      15:29:30,093 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57ff2d:781:49007978:129 aborting with 1 threads active!
      15:29:30,171 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: null
      15:29:30,171 ERROR [JDBCExceptionReporter] Transaction is not active: tx=TransactionImple < ac, BasicAction: -3f57ff2d:781:49007978:129 status: ActionStatus.ABORTING >; - nested throwable: (javax.resource.ResourceException: Transaction is not active: tx=TransactionImple < ac, BasicAction: -3f57ff2d:781:49007978:129 status: ActionStatus.ABORTING >)
      15:29:30,281 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_40] - Abort called on already aborted atomic action -3f57ff2d:781:49007978:129
      15:29:30,281 ERROR [TxConnectionManager] There is something wrong with the pooling?
      java.lang.IllegalStateException: afterCompletion called with wrong tx! Expected: TxSync11655404{tx=TransactionImple < ac, BasicAction: -3f57ff2d:781:49007978:129 status: ActionStatus.ABORTED > wasTrackByTx=true enlisted=true}, actual: null
      at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener$TransactionSynchronization.afterCompletion(TxConnectionManager.java:819)
      at org.jboss.resource.connectionmanager.TransactionSynchronizer.invokeAfter(TransactionSynchronizer.java:301)
      at org.jboss.resource.connectionmanager.TransactionSynchronizer.afterCompletion(TransactionSynchronizer.java:265)
      at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:136)
      at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:340)
      at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:107)
      at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:201)
      at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1378)
      at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
      at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
      at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:175)
      at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:87)
      at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
      at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
      at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:83)
      [/Code]

      What can I do to undo this error. Or can anybody tell me an other way to fix the problem?