High Availability Solution–Try it Now!

July 14 2009

3 comments 0
motif

Do you have high availability requirements for your Mule application? Mule High Availability provides basic failover capability for Mule. When the primary Mule instance become unavailable (e.g., because of a fatal JVM or hardware failure or it’s taken offline for maintenance), a backup Mule instance immediately becomes the primary node and resumes processing where the failed instance left off. After a system administrator has recovered the failed Mule instance and brought it back online, it automatically becomes the backup node.

Seamless failover is made possible by a distributed memory store that shares all transient state information among clustered Mule instances, such as:

  • SEDA service event queues
  • In-memory message queues

Mule High Availability is currently available for the following transports:

  • HTTP (including CXF Web Services)
  • JMS
  • WebSphere MQ
  • JDBC
  • File
  • FTP
  • Clustered (replaces the local VM transport)

To learn more about the high availability solution, check out the following resources:

Mule High Availability is available for Mule ESB Enterprise Platinum subscribers. To download a free evaluation copy on a trial basis, contact MuleSource.


We'd love to hear your opinion on this post


3 Responses to “High Availability Solution–Try it Now!”

  1. […] of which are listed here. We have also released version 1.0 of Mule High Availability, which we blogged about last month when we first made it available for customers to try […]

  2. Hi,

    Despite of that is an old thread, i still ask my question:

    Is there a limit of number of queue ? I have a problem with my ESB. I use more than 20 queues and when i switch the order of the queues to test, it never goes to the 20rst and more queue.

    Any solution ?
    Is it because i’m using the community version ?

    Thank you

  3. This is the perfect way to break down this inmfortaion.