WebSphere MQ connection pooling with Tomcat

Question

Tomcat has a built-in JDBC connection pooling, but unfortunately no built-in JMS connection pooling.

We are migrating a legacy Tomcat web application from WebSphere

Answer 1

I think you already know the answer.

option 1: Go with a Java EE application server. This has inbuilt JMS pools.

option 2: If this is a simple application that does a single job (like putting on a queue with fire and forget type), you can connect to the JMS provider (qmgr) and create the producer or consumer in the servlet_init method. This means the legacy code needs an update. You also need to take care of the reconnect when something breaks as JMS reconnect properties doesn't kick off a reconnection (as far as my experience goes).

option 3: I have gone with Spring's CachingConnectionFactory when the application happens to be more than a little complex than one in option 2. I have applications that use JMSTemplate and some doesn't.