I have deployed two similar applications in my JBoss portal server (4.3), which uses the same data source for Teradata connectivity.
But, one of the applications throw the following error:
18:32:40,144 WARN [loggerI18N] [com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.disallow] [com.arjuna.ats.internal.jta.transaction.arjunacore.lastReso
urce.disallow] Adding multiple last resources is disallowed. Current resource is org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource@1db9999
18:32:40,194 INFO [STDOUT] 18:32:40,194 ERROR Exception :
java.lang.Exception: geae.dao.GEAESQLException: org.jboss.util.NestedSQLException: Could not enlist in transaction on entering meta-aware object!; - nested throwable:
(javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: 3d13211:cc67:4cb
30a9a:454 status: ActionStatus.ABORT_ONLY >); - nested throwable: (org.jboss.resource.JBossResourceException: Could not enlist in transaction on entering meta-aware ob
ject!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, Ba
sicAction: 3d13211:cc67:4cb30a9a:454 status: ActionStatus.ABORT_ONLY >))
I also found fixes like adding <property name="com.arjuna.ats.jta.allowMultipleLastResources" value="TRUE"/> in the jbossjta-properties.xml file, which works.
But I am not supposed to edit the server files, as per some policy.
But is there any solutions where in i can fix this within the application? Why this error happens only for the 2nd application which is very similar to the 1st one?
Thanks!! Appreciate all your responses!!
Joined: Oct 14, 2009
Is there anyone who thinks why this could be happening differently between applications.
Thanks for your reply. But, I have already tried that solution and it works. I have also tried "<datasources><no-tx-datasource>" which works.
I need a solution where my solution should be incorporated within the EAR / application file.