Network Deployment (Distributed operating systems), v8.0 > Reference > Administrator best practices
Performance for v5 default messaging queues
To optimize performance, configure the JMS queue destination properties to best fit your WAS Version 5 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, ensure that you configure the queue destination properties adequately for the application usage.
For queue destinations configured on a WAS v5 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 that 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 the Handle poison messages in WebSphere MQ classes for JMS and Script (MQSC) sections in the WebSphere MQ information center.
Configure a queue for v5 default messaging
Related
WebSphere MQ library