To optimize performance, configure the queue 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.
For
queue destinations configured on a WebSphere Application Server Version
5 node, you should also consider queue attributes of the internal
JMS server that are associated with the queue name. Inappropriate
queue attributes can reduce the performance of WebSphere operations.
- BOQNAME
- The excessive backout requeue name. This can be set to a local
queue name that can hold the messages which were rolled back by the
WebSphere applications. This queue name can be a system dead letter
queue.
- BOTHRESH
- The backout threshold and can be set to a number once the threshold
is reached, the message will be moved to the queue name specified
in BOQNAME.
For
more information about using these properties, see:
- "Handling poison messages" in the WebSphere MQ Using
Java book
- The WebSphere MQ Script (MQSC) Command Reference book