I have a situation where a JMS queue that is processing transactions into our ECC system, needs to process one transaction at a time. The JMS queue is set to 1 concurrent process but since we have two run time nodes, it appears that each node is processing one transaction at a time.
We receive transactions from an external Plant system thru Cloud Integration. These transactions are routed to a JMS Queue to post into our ECC backend system. The proxy in ECC is set up as synchronous so that the next transaction isn't submitted until the first has completely processed. Since we have two run time nodes, we are actually receiving transactions from each node, one at a time. This is causing the transactions to fail with user locks since each transaction running may be for the same process order.
Has anyone ran into this issue before and if so, how can it be addressed?
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.