users@glassfish.java.net

Re: JMS connection pool problem / bug?

From: <glassfish_at_javadesktop.org>
Date: Mon, 16 Feb 2009 04:57:42 PST

> Does anyone use JMS on Glassfish?

Yes, but they probably doesn't run in to your problems when they use it on the server side. I haven't read your code(!) but you probably doesn't get what you expect from your JNDI look up. You expect a plain ConnectionFactory (maybe a QueueConnectionFactory) but what you get is something wrapped in JMSJCA with a built in pool. On the server this i probably fine where multiple components running in the same jvm share the same pool but you get several pools on several jvms which i guess is pointless for you.

You could set up a separate connection factory for your clients with "Initial and Minimum Pool" = 1.

You could use a different object store and bypass JMSJCA and Glassfish completely or you could tie your code directly (new instead of JNDI look up) to Open MQ which Glassfish uses for JMS messaging.
[Message sent by forum member 'perror' (perror)]

http://forums.java.net/jive/thread.jspa?messageID=332052