Modify these MQ settings to improve your performance.
Procedure
- Change the enterpriseOutputListener and enterpriseInputListener
properties.
- In the WebSphere® Application Server administrative console, click .
- Click enterpriseOutputListener and
change the maximum sessions to 3, maximum retries
to 2, and maximum messages to 10.
- Click enterpriseInputListener and
change the maximum sessions to 2, maximum retries
to 2, and maximum messages to 10.
- Modify the Log buffer pages setting
in the queue manager.
- In the MQ Explorer, right-click IBM.DC.QM and
select Properties.
- Click Log, and then change the
value of Log buffer pages to 4096.
- Click OK.
- Open the qm.ini file in a text
editor.
- Modify the setting for log buffer pages to LogBufferPages=4096.
- 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.
- 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.
- In the MQ Explorer, right-click IBM.DC.QM and
select Properties.
- Click TCP, and then change the
value of TCP keepalive to Yes.
- Click OK.
- Open the qm.ini file in a text
editor.
- Modify the setting for TCP keepalive to KeepAlive
= Yes.
- 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.
- Modify the Max channels setting
in the queue manager.
- In the MQ Explorer, right-click IBM.DC.QM and
select Properties.
- Click Channels and change the
value of the Max channels to 1000.
- Click OK.
- Open the qm.ini file in a text
editor.
- Modify the setting for maximum channels to MaxChannels=1000.
- 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.
- Restart the IBM®.DC.QM
queue manager.
- Modify the Purge policy setting
of the queue connection factory connection pool.
- In the WebSphere Application Server administrative console, click .
- Click IBMDCQM.
- Under Additional Properties,
click Connection pool.
- 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.
- Save your configuration changes and restart WebSphere Application Server.