1 2 Previous Next 19 Replies Latest reply on Jul 13, 2007 5:25 AM by ysiraj Go to original post
      • 15. Re: 4.0.5 to 4.2.0 upgrade and JBossTS

        When I was using local-tx I ran into the "only one local tx" issue and since that was more of a temporary problem as I wanted to move to a better transaction model anyway I didn't want to dig too deeply into that.

        However your classloading comment got me to look closer at the mysql driver and I have found out that this only happens with entity beans that rely on auto incremented ID columns. - If i manually assign a key I can create entity beans just fine.

        I am still looking into why this is happening and how it can be resolved.

        • 16. Re: 4.0.5 to 4.2.0 upgrade and JBossTS

          jhalliday: Sorry about the late response. I added the following to jbossjta-properties.xml

          <property name="com.arjuna.ats.jta.allowMultipleLastResources" value="true"/>

          as the first child element of
          <properties depends="arjuna" name="jta">

          which I assume is the correct place (the documentation does not say exactly where).

          The DeploymentException I get occurs at JBoss startup, as the transaction manager is started.


          • 17. Re: 4.0.5 to 4.2.0 upgrade and JBossTS


            I'm not able to reproduce that. What you should get at startup is:

            10:30:07,036 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
            10:30:07,036 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
            10:30:07,297 INFO [TransactionManagerService] Starting recovery manager
            10:30:07,505 INFO [TransactionManagerService] Recovery manager started
            10:30:07,505 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
            10:30:29,926 WARN [loggerI18N] [com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.startupWarning] [com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.startupWarning] You have chosen to enable multiple last resources in the transaction manager. This is transactionally unsafe and should not be relied upon.

            The last message there indicates the config param is being picked up correctly.

            • 18. Re: 4.0.5 to 4.2.0 upgrade and JBossTS

              I cannot reproduce it either - it works!

              This is strange since it failed twice previously and all I did now was re-enable the code that previously failed. I hope it was simply a typo.

              Thank you for your patience and help

              • 19. Re: 4.0.5 to 4.2.0 upgrade and JBossTS

                Has anyone been able to resolve this issue? I'm having the exact same issue which "helgaw" made i.e. java.lang.IllegalArgumentException: object is not an instance of declaring class

                i've mysql tables with auto-increment pk.

                1 2 Previous Next