6.6. Message Ordering in the Cluster

PDF

To ensure messages are consumed in the same order they were produced, set strict JMS ordering by setting the DefaultPreserveOrdering Server Peer attribute to true. While set to true, messages cannot be distributed as freely around the cluster. The default value is false.

Github

Youtube

Twitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.