Configuring WebSphere MQ connection pooling

Browse or change properties of WebSphere MQ connection pooling for JMS connections from an application server to WebSphere MQ as a JMS provider.

About this task

To improve the overall performance of JMS within the system, WebSphere MQ connection factories can be configured to use the connection pooling facility provided by the WebSphere MQ JMS implementation.

This support for connection pooling does not affect the performance of a JMS application that uses WebSphere MQ, because it retains its connections while listening on a destination. However, it does affect the overall JMS system performance. When a connection is no longer required and is removed from the application server's connection pool, WebSphere MQ can pool the underlying connection to the queue manager and reuse it later instead of destroying it.

To enable WebSphere MQ connection pooling, the enable MQ connection pooling property must be selected on the connection factory used to create connections to WebSphere MQ.

Note: When a connection has been created from a connection factory that has the enable MQ connection pooling property selected, the WebSphere MQ connection pooling is switched on for the entire application server. Any JMS connections created to WebSphere MQ when the pool is active are automatically pooled, regardless of whether the enable MQ connection pool property is set on the connection factory used to create the connection.
Note: This support is only available for use with WebSphere MQ as a JMS provider.
Note: If a firewall is being used that closes idle connections, the total of the unused timeout configured on the WebSphere Application Server connection pool and the MQJMS.POOLING.TIMEOUT configured in WebSphere MQ connection pooling must be less than the idle timeout configured on the firewall to allow connections to be cleaned up by the connection pools, rather than being terminated by the firewall.

To configure WebSphere MQ connection pooling for an application server, use the administrative console to complete the following steps:

Procedure

  1. Display the Message Listener Service properties for the application server
    1. In the navigation pane, click Servers > Application Servers
    2. In the content pane, click the name of the application server.
    3. Under Additional Properties, click Message Listener Service properties.
  2. Select Custom Properties, to enable WebSphere MQ connection pooling, add the following custom properties:
    MQJMS.POOLING.THRESHOLD
    The maximum number of unused connections in the pool.
    MQJMS.POOLING.TIMEOUT
    The timeout in milliseconds for unused connections in the pool.
  3. Click OK.
  4. Save any changes to the master configuration.
  5. To have the changed configuration take effect, stop then restart the application server.

What to do next

For additional information, see the books in the WebSphere MQ library http://www.ibm.com/software/integration/wmq/library/.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 5:25:00 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-base-dist&topic=tmj_mqcon
File name: tmj_mqcon.html