0 Replies Latest reply on Oct 1, 2009 1:12 PM by Joerg Glandorf

    Always creating new transaction between inter-EAR calls

    Joerg Glandorf Newbie

      We are using Springs JtaTransactionManager bound to

      [org.springframework.transaction.jta.JtaTransactionManager] Using JTA TransactionManager: com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate@114304e

      Things are fine when a service method calls another service of the same ear:
      DEBUG [org.springframework.transaction.jta.JtaTransactionManager] Participating in existing transaction

      Tx Propagation seems NOT to work when service of EAR-A calls service (SLSB) in EAR-B.
      Tx Attributes are always PROPAGATION_REQUIRED,ISOLATION_DEFAULT
      I always get a
      [org.springframework.transaction.jta.JtaTransactionManager] Creating new transaction with name ...

      and checking status reports always NO_TRANSACTION

      I wonder if this is the regular behaviour when using JTA (I assume not).

      I checked the status of the tx in the service method being called
      with

      UserTransaction ut2 = (UserTransaction) new InitialContext().lookup("UserTransaction");
      int txStatus = ut2.getStatus();
      but only get NO_TRANSACTION.
      (For this test I removed all spring interceptor names from my bean)
      Any hints are appreciated why the tx is not propagated to the other ear's.
      Has anybody seen the same problem ?