Troubleshooting
Problem
When using a message-driven bean (MDB) to get messages from a IBM WebSphere MQ, some messages take significantly longer to be removed from the queue and processed by the MDB. This technote does not apply to the Default Messaging Provider and applies for those using below MQ version 7.
Cause
The WebSphere Application Server message listener service is instrumented so that the thread browsing the queue for messages skips a message if all message consumers (MDBs) are busy or if the message has not yet been committed to the queue. It returns to the skipped messages when it re-scans the queue. The problem is that by default, the thread waits 5000 milliseconds before re-scanning the queue.
Resolving The Problem
Change the eoqTimeout value to 0. With this set, the thread will not wait before rescanning the queue and processing the messages.
Follow these instructions to set eoqTimeout to 0:
- Expand Servers, click on Application Servers, and then select your server in the WebSphere administrative console.
- Select Process Definition.
- Select Java™ Virtual Machine.
- Select Custom Properties, and then click New.
- Add the property com.ibm.mq.jms.tuning.eoqTimeout with a value of 0. The value of the eoqTimeout is in milliseconds. If it is set to a value other than 0, the minimum value is 1000 milliseconds.
- Click OK and save your configuration.
- Restart the application server.
If consistently slower MDB performance is observed as the number of messages sent to the queue increases, increase the Maximum Sessions on the listener port so that more messages are processed concurrently.
Use the solution described in this technote only if the problem is intermittent and independent of load.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21190601