IBM Support

webMethods Knowlegebase : Concurrent JMS trigger processing serially (1746716)

Troubleshooting


Problem

JMS messages on a JMS queue seem to be processed serially, despite the fact the the processing JMS trigger is defined as concurrent with max threads = 10. No JMS message selector, no joins, no local filter, one (time consuming) service to process. The trigger is defined with max prefetch size = 10.

To reproduce you can put multiple JMS messages on a queue with a disabled trigger. After enabling the trigger the messages on the queue seem to be processed serial.

The JMS trigger service must be time consuming to be able to do the checks:

- put some messages on the JMS queue

- open MWS and browse the queue ( the messages, all status "available")

- enable the JMS trigger

=> Now one message will be processed (removed from queue), the other messages remain in the queue with status unAck (not acknowledged).

Document Location

Worldwide

[{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSVYEV","label":"IBM webMethods Integration"},"ARM Category":[{"code":"a8mKe00000000AQIAY","label":"webMethods Broker (PIF)"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Red Hat Enterprise Linux"}],"Version":"8.2.2"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
20 March 2025

UID

ibm17206665

Page Feedback