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 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952287#3952287 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952287 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
