This content has been marked as final.
Show 2 replies
-
1. Re: standalone client pooling of JMS resources
vandana_awat Mar 26, 2009 5:28 AM (in response to jonroler)Did you find a solution to the issue. I am facing a similar issue, any pointers would be helpful.
-
2. Re: standalone client pooling of JMS resources
timfox Mar 26, 2009 5:33 AM (in response to jonroler)Pooling of JMS connections is handled by the JMS JCA adapter *not* JBoss Messaging.
The JBoss JMS RA only works in the app server / servlet container, it does not work standalone. There are other JMS JCA adapters that do work standalone (google)
If you want XA transactions on the client side, you will also need a transaction manager on the client side plus a recovery manager.
You're half way to requiring an app server on the client side!
If that's what you really need then you could deploy a stripped down version of JBoss AS on the client side.