[jboss-user] [JBoss Messaging] - Re: Opening a new JMS session for an already existing transa

[olimo]

Hello, 
thx for your answer, we finally had time to try a version using XA. 

We tried to share in cluster the XAConnection so that when a node fails the transaction can continue on the other nodes using this shared connection: 


  | XASession session = mySharedXAConnection.createXASession();
  | XAResource resource = session.getXAResource();
  | resource.start(mySharedXID, XAResource.TMJOIN);
  | 

Nevertheless, we got the following error when doing the mySharedXAConnection.createXASession();


  | 
  | 18:17:52,375 INFO  [STDOUT] java.lang.NullPointerException
  | 18:17:52,375 INFO  [STDOUT]     at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:87)
  | 18:17:52,375 INFO  [STDOUT]     at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
  | 18:17:52,375 INFO  [STDOUT]     at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
  | 18:17:52,375 INFO  [STDOUT]     at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
  | 18:17:52,375 INFO  [STDOUT]     at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
  | 18:17:52,375 INFO  [STDOUT]     at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
  | 18:17:52,375 INFO  [STDOUT]     at org.jboss.jms.client.delegate.ClientConnectionDelegate.createSessionDelegate(ClientConnectionDelegate.java)
  | 18:17:52,375 INFO  [STDOUT]     at org.jboss.jms.client.JBossConnection.createSessionInternal(JBossConnection.java:269)
  | 18:17:52,375 INFO  [STDOUT]     at org.jboss.jms.client.JBossConnection.createXASession(JBossConnection.java:198)
  | 
(We are using EAP 4.3.0)
 
May someone help us to understand what's wrong with this method?

If we create again a new XAConnection on the same JBM cluster, we do not get the same XARessource (i.e. our Xid is not recognized when doing the JOIN). 

Is it possible to get back an XARessource that accept the Xid we declared in the failed node? 



olivier



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

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