Exclusive Consumer, Exclusive Queues

Exclusive Consumer, Exclusive Queues

In Apache ActiveMQ, Exclusive Consumer or Exclusive Queues avoids the end user having to pin anything.

The broker will pick a single MessageConsumer to get all the messages for a queue to ensure ordering. If that consumer fails, the broker will auto failover and choose another consumer.

So the effect is a heterogeneous J2EE cluster where each JVM has the same setup and configuration; the broker is choosing one consumer to be the master and send all the messages to it in order until it dies; then you get immediate failover to another consumer.

For those who've struggled with pinning JMS consumers in J2EE clusters you'll immediately realize how useful this is to making clustered, high available distributed services.

Exclusive Consumer, Exclusive Queues
added 10 years 5 months ago

- SciPy
- Apache ZooKeeper
- Apache Hive
- Apache Ambari
- Oracle Coherence
- Internet Information Services (IIS)
- ClickOnce Deployment
- C++11, C++0x
- Knockout, KnockoutJS
- Entity Framework (EF)
- Extensible Stylesheet Language (XSL)
- Simple Object Access Protocol (SOAP)
- JXTA (Juxtapose)
- Transmission Control Protocol (TCP)
- Geronimo
- Exclusive Consumer, Exclusive Queues
- Subversion (SVN)
- Log4j, Log4Java
- Google Mocking Framework (GMock)
- Apache ActiveMQ