For SOAP over JMS transactions, is there any way to control the thread count that can be utilized for controlling the messages that are picked from UM.
We tried setting the Max Thread Count in trigger settings. But the result was not as expected.
Eg: We had set the Max Thread Count to 3. However we publish 20 msgs to UM all were getting picked from the UM.
Ideally the trigger should have waited for the already running instances to be completed first before picking up the new set.
If this property is for the messages that are already retrieved from UM. So is there any way to control how the messages will be retrieved from the UM?