+

Search Tips   |   Advanced Search

 

Configure WebSphere MQ connection pooling

 

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

 

Overview

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 appserver'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.

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 appserver. 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.

This support is only available for use with WebSphere MQ as a JMS provider.

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

 

Procedure

  1. Display the Message Listener Service properties for the appserver

    1. In the navigation pane, click Servers > Application Servers

    2. In the content pane, click the name of the appserver.

    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 appserver.

 

What to do next

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


}

 

Related concepts


Asynchronous messaging using JMS - overview

 

Related tasks


Configure JMS resources for the WebSphere MQ messaging provider
Configure JMS resources for the WebSphere MQ messaging provider