[timfox]

Please elaborate on your comment:

I am using XAConnectionFactory as suggested by you, but I get MessagingJMSException

Please post your code

[dv_lakshmi]

The stacktrace is

org.jboss.jms.util.MessagingJMSException: Cannot start callbackserver after 50 retries at org.jboss.jms.client.remoting.JMSRemotingConnection.<init>(JMSRemotingConnection.java:153) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.invoke(ClientConnectionFactoryDelegate.java:158) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N6840474864420126404.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N6840474864420126404.java) at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:80) at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N6840474864420126404.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N6840474864420126404.java) at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:69) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N6840474864420126404.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N6840474864420126404.java) at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N6840474864420126404.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N6840474864420126404.java) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:203) at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:109) at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:104) at org.sturim.xltester.common.Publisher.initializeJMS(Publisher.java:307) at org.sturim.xltester.common.Publisher.init(Publisher.java:173) at org.sturim.xltester.test.Test$ExecutionDaemon.run(Test.java:1408) at java.lang.Thread.run(Unknown Source)

and the client code is as a simple jms client would be . The connectionFactory name is XAConnectionFactory

 try {
 conFactory = (QueueConnectionFactory) initialcontext.lookup(connectionFactory);
 } catch (CommunicationException e) {
 System.out.println("Connection Factory " + connectionFactory);
 //initialcontext.
 throw e;
 }
 con = ((QueueConnectionFactory) conFactory).createQueueConnection();

Please note that it fails in the line where its trying to get a queue connection.

[timfox]

Ok, so this is not related to it being an XAConnection, this is because you are using the socket transport which will attempt to start a server on the client to receive callbacks for messages.

As I say, this is probably failing beacuse jnlp won't let you start a server and open server sockets on the client side.

JBoss MQ worked around this kind of problem by having a transport called UIL2 which used the same TCP connection for 2 way traffic.

Currently there is no such transport in JBoss Messaging, but it is on the roadmap to be implemented.

Also the HTTP transport (which is also scheduled) may help you here since it only does client to server requests and polls the server for new messages.

See http://jira.jboss.com/jira/browse/JBMESSAGING-92