FuseESB and ActiveMQ

Solution Unverified - Updated -


FuseESB and ActiveMQ(AMQ - JMS Provider, aka Fuse Message Broker) run as independent systems that start up and shutdown in separate JVMs. Message loss can occur if AMQ is down and FuseESB is running and vice versa (AMQ running and receiving messages through the JMS API - AMQ persistence store can fill up if FuseESB is not processing messages). What is the best approach to deal with these situations?

Our current thought is to create a custom camel route that runs in FuseESB and performs JMX MBean calls to monitor the state of AMQ. If AMQ is detected to be down then the custom route will stop FuseESB.


Fuse ESB
Jboss Fuse 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content