WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Changing MQ settings to improve performance

Modify these MQ settings to improve your performance.

Procedure
  1. Change the enterpriseOutputListener and enterpriseInputListener properties.
    1. In the WebSphere® Application Server administrative console, click Application servers > server1 > Messaging > Message Listener Service > Listener Ports.
    2. Click enterpriseOutputListener and change the maximum sessions to 3, maximum retries to 2, and maximum messages to 10.
    3. Click enterpriseInputListener and change the maximum sessions to 2, maximum retries to 2, and maximum messages to 10.
  2. Modify the Log buffer pages setting in the queue manager.

    Windows

    1. In the MQ Explorer, right-click IBM.DC.QM and select Properties.
    2. Click Log, and then change the value of Log buffer pages to 4096.
    3. Click OK.

    Linux

    1. Open the qm.ini file in a text editor.
    2. Modify the setting for log buffer pages to LogBufferPages=4096.
    3. Save your changes.

    Refer to the Queue manager configuration files topic in the WebSphere MQ information center for more details about the queue manager configuration file settings.

  3. Modify the TCP keepalive setting in the queue manager.

    The TCP keepalive setting determines whether TCP/IP periodically checks to make sure that the other end of the connection is still available. If the other end is not available, the channel is closed.

    Windows

    1. In the MQ Explorer, right-click IBM.DC.QM and select Properties.
    2. Click TCP, and then change the value of TCP keepalive to Yes.
    3. Click OK.

    Linux

    1. Open the qm.ini file in a text editor.
    2. Modify the setting for TCP keepalive to KeepAlive = Yes.
    3. Save your changes.

    Refer to the Queue manager configuration files topic in the WebSphere MQ information center for more details about the queue manager configuration file settings.

  4. Modify the Max channels setting in the queue manager.

    Windows

    1. In the MQ Explorer, right-click IBM.DC.QM and select Properties.
    2. Click Channels and change the value of the Max channels to 1000.
    3. Click OK.

    Linux

    1. Open the qm.ini file in a text editor.
    2. Modify the setting for maximum channels to MaxChannels=1000.
    3. Save your changes.

    Refer to the Queue manager configuration files topic in the WebSphere MQ information center for more details about the queue manager configuration file settings.

  5. Restart the IBM®.DC.QM queue manager.
  6. Modify the Purge policy setting of the queue connection factory connection pool.
    1. In the WebSphere Application Server administrative console, click Resources > JMS > Queue connection factories.
    2. Click IBMDCQM.
    3. Under Additional Properties, click Connection pool.
    4. Set the Purge policy to EntirePool. When the purge policy is set to EntirePool, the WebSphere connection pool manager flushes the entire connection pool when a fatal connection error, such as Reason Code 2009, occurs. This prevents the application from getting other bad connections from the pool.
    5. Save your configuration changes and restart WebSphere Application Server.

Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.