• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

ActiveMQ, Queue Failover Question

 
author
Posts: 23951
142
jQuery Eclipse IDE Firefox Browser VI Editor C++ Chrome Java Linux Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Just had a conversation with a friend about the ActiveMQ failover mechanism. He told me that ActiveMQ depends on the Veritas Cluster, in order to handle failover. This doesn't sound right to me, as it seems really clunky.

So... is this true? Does it depend on a cluster failover system? Or does the ActiveMQ queues have a synchronization and heatbeating system, for alternate queues to take over the queuing when the primary queues fail?

Thanks,
Henry
 
author
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In ActiveMQ, failover is commonly used to refer to the Failover Transport. Based on your question, I suspect that you are referring to ActiveMQ Master/Slave and, more specifically, Shared File System Master Slave. This is the only thing that would refer to disk storage in ActiveMQ besides message persistence and you haven't mentioned that.

The ActiveMQ shared filesystem master/slave functionality utilizes a shared filesystem to provide a high availability configuration. The only requirement is that the filesystem support locking. Using the shared filesystem to store broker data, many instances of ActiveMQ can be pointed at the same data store location on the filesystem. The first broker instance that gets a lock on the data store location is considered the master and any other brokers pointed at this same location will remain in a warm standby state. If the master broker fails, then the lock on the data store location is released and the next broker to grab the lock will become the new master. There are some diagrams demonstrating this functionality in the Shared File System Master Slave doc. And there's some more information in ActiveMQ In Action.

Bruce
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic