JMS Connecting/Disconnecting to Websphere MQ

Does anyone know the specific configurations that are needed to avoid continuous connecting/disconnecting to Websphere MQ? We have multiple JMS triggers that are using the same JMS Connection Alias and are wanting them to use a connection pool which I thought should maintain the connections and not require reconnecting.

Any information anyone has would be great, I’ve found various settings on the connection alias, extended settings on the IS itself and when creating the queue connection factory. Unfortunately the documentation isn’t helping to know for sure what setting would give us a constant connection.

We had 23 JMS triggers listening and processing messages and it taxed the mainframe’s CPU where MQSeries is running that we’re connecting to from Linux via webMethods IS.