Performance considerations for WebSphere MQ topic destinations
To optimize performance, configure the topic destination properties to
best fit your applications. For example, setting the Expiry property to SPECIFIED
and the Specified Expiry property to 30000 milliseconds for the expiry timeout,
reduces the number of messages that can be queued. To ensure that there are
enough underlying WebSphere MQ resources available for the queue, you must
ensure that you configure the queue destination properties adequately for
your application usage.
- Ensure the queue attribute, INDXTYPE is set to MSGID for the following
system queues:
- SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE
- SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE
- Ensure the queue attribute, INDXTYPE is set to CORRELID for the following
system queues:
- SYSTEM.JMS.ND.SUBSCRIBER.QUEUE
- SYSTEM.JMS.D.SUBSCRIBER.QUEUE
For more information about using these properties, see:
- The WebSphere MQ Using Java book
- The WebSphere MQ Script (MQSC) Command Reference book
Searchable topic ID:
rmj_adm28
Last updated: Jun 21, 2007 9:56:50 PM CDT
WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/rmj_adm28.html