1 Reply Latest reply on Nov 13, 2015 7:06 AM by Tom Jenkinson

    JTA problem in Wildfly8.1 with DB2 AS400 V6R1

    Suresh M Newbie

      We are porting an application(EJB2.1) from Websphere 6.1 / DB2 AS400 V6R1 to Wildfly8.1 with DB2 AS400 V6R1. JT400.jar as jdbc driver in both WAS and JBOSS. The transactions are getting partilally commited in Wildfly8.1 and JBOSS 7.1 application server.

       

      Setrollbackonly() is getting invoked @ejb level but the transaction at the DB2 is getting committed. The same behavior for all the transaction attributes viz, Requires New , Requires and Mandatory.

       

      Below is the Datasource used.

       

      <datasource jta="true" jndi-name="java:/jdbc/DEPWBDS" pool-name="DEPWBDS" enabled="true" use-ccm="false">

      <connection-url>JDBC URL;packageCCSID=13488;</connection-url>

      <datasource-class>com.ibm.as400.access.AS400JDBCDataSource</datasource-class>

      <driver>jt400.jar</driver>

      <security>

      <user-name>*******</user-name>

      <password>**********</password>

      </security>

      <validation>

      <validate-on-match>false</validate-on-match>

      <background-validation>false</background-validation>

      </validation>

      <statement>

      <share-prepared-statements>false</share-prepared-statements>

      </statement>

      </datasource>

       

      Please help us in resolving this issue.

       

      Thanks,

      Suresh

        • 1. Re: JTA problem in Wildfly8.1 with DB2 AS400 V6R1
          Tom Jenkinson Master

          Hi Suresh,

           

          This seems more likely related to app code than anything perculiar in the transaction manager so I have moved it to the user forum of WildFly.

           

          What I can say:

          1. Please replicate this on a more recent version of WildFly. WildFly 10 CR4 was recently released or WFLY 9 if you absolutely must use a .Final

          2. You will need to provide more code, ideally a replicator

          3. Please include a trace level log

           

          Thanks,

          Tom