[jboss-user] [EJB/JBoss] - Re: Problem with arjuna API

[venuwin]

Just adding some more information for your reference so that i might be helped.

After reading through some forums, i concluded that XA datasource could solve the issue and switched to it by taking the mysql5.1.7 jar file and modifying my XML to look like this :


  | <?xml version="1.0" encoding="UTF-8"?>
  | <datasources> 
  | 	<xa-datasource>
  | 		<jndi-name>CatMgrDS</jndi-name>
  | 		<xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
  | 		<xa-datasource-property name="URL">jdbc:mysql://192.168.157.57:3306/confmanager</xa-datasource-property>
  | 		<xa-datasource-property name="User">root</xa-datasource-property>
  | 		<xa-datasource-property name="Password">root</xa-datasource-property>
  | 			<!-- the minimum size of the connection pool -->  
  | 		 <min-pool-size>1</min-pool-size> 
  | 		 <!-- The maximum connections in a pool/sub-pool -->  
  | 		 <max-pool-size>4</max-pool-size> 
  | 	</xa-datasource>
  | </datasources>
  | 
getting this error multiple times though :
16:42:59,861 WARN  [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
  | 
  |  after which i get  16:43:06,111 ERROR [JmsServerSession] org.jboss.resource.adapter.jms.inflow.JmsServerSession at ef43f1 failed to commit/rollback
  | javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Could not commit transaction.
  |         at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1426)
  |         at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
  |         at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
  |         at org.jboss.resource.adapter.jms.inflow.JmsServerSession$XATransactionDemarcationStrategy.end(JmsServerSession.java:498)
  |         at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:243)
  |         at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
  |         at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
  |         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
  |         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
  |         at java.lang.Thread.run(Thread.java:619)
  | 

Is there anything i have to touch in my code for this Tx not to be rolled back? It is really bothering to struggle with such issues while migrating to a higher version of Jboss. Any help folks ?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4208134#4208134

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4208134