Serialization of JMS Message Processing in Project Migrated from Java CAPS

(Doc ID 1922480.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


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.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms