JMS Messages in a Queue with Protected Concurrency are not being Processed in Order
(Doc ID 1549971.1)
Last updated on JANUARY 30, 2020
Applies to:Oracle Java CAPS Enterprise Service Bus - Version R6.3 and later
Information in this document applies to any platform.
There are Java Messaging Service (JMS) message (mgs)s in five different queues (que_TCMSMUX_0, que_TCMSMUX_1, que_TCMSMUX_2, que_TCMSMUX_3, que_TCMSMUX_4) and there are five different subscribers from different Java Collaboration Definition (JCD)s with five thread on each.
All five queues are processed in protected concurrency mode. However, msgs from different routes in the same queue such as que_TCMSMUX_0 next to each other are not processed in serial mode, i.e. second JMS msg from different route2 starts before the first JMS msg from route1 finishes.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document