Serialization of JMS Message Processing in Project Migrated from Java CAPS
(Doc ID 1922480.1)
Last updated on MARCH 30, 2019
Applies to:
Oracle SOA Suite - Version 11.1.1.7.0 and laterInformation in this document applies to any platform.
Symptoms
A project is migrated from Java CAPS to SOA using Spring Beans for processing and JMS queues for input and output.
When running in a clustered environment using Uniform Distributed Destinations (UDD) it is observed that even with the singleton property set to true and number of threads set to 1 for the inbound JMS Adapter, messages are processed in parallel.
However, the requirement is to serialize the message processing, so that only one single message is processed at a time, and the next message is not picked before the previous one is completed.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |