2 Replies Latest reply on Mar 26, 2009 5:33 AM by timfox

    standalone client pooling of JMS resources

    jonroler

      I have a working standalone JBM 1.4 java client application that publishes messages to a JBoss Application Server running JBM. It is a multithreaded application that will eventually produce (not receive) messages at a pretty high rate, so I will require some form of client-side caching/pooling of JMS connections/sessions/producers. Does JBM provide any support for pooling of JMS resources in a standalone java client? If JBM doesn't have any client-side JMS resource pooling support, can you recommend any other libraries that might be applicable? I'd rather not have to write this myself.

      I doubt this affects the answer, but I'll also mention (just in case) that my standalone java client also writes to the database and will need to use XA transactions so that database writes and the publishing of JMS messages are atomic.

        • 1. Re: standalone client pooling of JMS resources

          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

            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.