2 Replies Latest reply on Mar 27, 2012 5:27 AM by Maciej Swiderski

    AS 7.1.1.Final different UserTransaction in JNDI

    Maciej Swiderski Master



      I noticed that in AS 7.1.1.Final UserTransaction that is returned from JNDI look up is different that one in AS 7.0.2>


      7.1.1 is org.jboss.tm.usertx.client.ServerVMClientUserTransaction


      and on 7.0.2 is com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple.


      And this seems to cause me some troubles on the application side. On commit some fields on an abject are reset (at least I was able to observe such behavior). Why that has changed and can it be somehow configured to use arjuna usertransaction be default or any other thoughts are more than welcome.




        • 1. Re: AS 7.1.1.Final different UserTransaction in JNDI
          jaikiran pai Master

          The internal implementation class shouldn't really be a concern to the application code. If it does, that we should find out what the real issue is. Can you explain a bit more about what you are running into?

          1 of 1 people found this helpful
          • 2. Re: AS 7.1.1.Final different UserTransaction in JNDI
            Maciej Swiderski Master

            After bit more digging into the issue it turned out it is not a matter of implementation class of UserTransaction but missing TransactionManager bound to expected JNDI context. In 7.0.2 it was bound to java:jboss/TransactionManager and in 7.1.1 it is bound to java:/TransactionManager


            So, in fact on 7.1.1 transaction manager was found and transaction synchronization was registered and on commit (after completion) there was additional logic executed on application side causing reset of mentioned fields.


            Thanks, I consider this as answered as it has nothing to do with different implementation classes of UserTransaction.