Announcing Mule 3.2

September 13 2011


It’s Saturday night. You realize you don’t have your cell phone and won’t be able to check on your fulfillment system. Chuckling, you remember without nostalgia the electric panic that used to set in over such a conundrum. Now you don’t give it a moment’s thought. After the weekend you arrive to work and try to avoid that blinking little red light, always in the periphery, nagging from the telephone set. Twenty-three more irate complaints demanding tedious, manual data forensics? Hardly, just a happy customer congratulating you on the vast improvement in your support center.

A dream? No, Mule 3.2 is here! The Mulesoft team is overjoyed to announce Mule 3.2, chock full of goodies for the enterprise and the Mule community.

High Availability Clustering

Ensuring zero message loss is a primary concern when you’re building mission-critical applications. Mule 3.2 provides key capabilities to support these applications. These capabilities include:

  • High availability clustering to ensure system-level availability
  • Reliability patterns for non-transactional connectors


Mule ensures system availability by clustering together Mule ESB servers into one virtual server composed of multiple nodes. The acts as a unit, communicating and sharing information through a distributed shared memory data grid. If a node becomes unavailable due to failure or planned downtime, another node in the cluster can assume the workload and continue to process existing events and messages. Because all nodes in a cluster process messages simultaneously, clusters can also improve performance and . Compared to a single node instance, clusters can support more users or improve application performance by sharing the workload across multiple nodes or by adding nodes to the cluster.

Reliability Patterns

A zero-message loss application not only requires the underlying ESB to be reliable, but that reliability needs to extend to individual connections. New reliability patterns introduced in Mule 3.2 give you the tools to build fully reliable applications in your clusters. The Mule 3.2 documentation provides code examples that show how you can implement a reliable message pattern for a number of different non-transactional transports, including HTTP, FTP, File, and IMAP. (Mule’s built-in support for transactional transports such as JMS enables reliable messaging for applications that use these types of transports.)

Business Event Analyzer

Many businesses require accurate analysis of business events. Some use case examples include:

  • Root cause analysis
  • Regulatory compliance
  • Business activity monitoring
  • Business intelligence

Mule gives you in-depth visibility into business transactions and events on your Mule servers. This visibility is available out of the box in the Business Events tab in the management console. However, it can also be integrated with other applications through storage in a persistent database. You can track events for the flows and message processors handling your business transactions and drill down into event-related data to do things like analyze the root cause of failures, isolate performance bottlenecks, and test for compliance to company procedures.

Enterprise Nirvana

With the availability, reliability, , and visibility provided by Mule 3.2 you can achieve peace-of-mind that only comes from a truly world-class enterprise system.

But There’s Even More!

  • Store and Forward with the new until-successful message processor.  You can use the until-successful to retry an operation until it succeeds. For example, you can configured it to send a message to an outbound endpoint until the send succeeds.

Download Mule 3.2

Download Mule 3.2 at Be sure to check out what’s new in Mule 3.2 for detailed information on this release.

We'd love to hear your opinion on this post

9 Responses to “Announcing Mule 3.2”

  1. Lots of good stuff in there, thank you!

    Couple of questions:

    – In a cluster, how are polling endpoints controlled? You can’t have polling occurring simultaneously in different nodes so does clustering take care of ensuring only one instance of the polling endpoints exists?

    – What is a Mule plugin? How is it different from a module? Is it lower level? If yes, when do you create plugins and how?


    PS. You have “Drools” twice in the list of goodies 🙂

  2. I can answer the plugin portion of the comment.

    Mule Plugins are indeed Mule Modules. They are just packaged differently.

    A Mule Plugin is packaged as a ZIP file which contains in it the Mule Module and all the dependencies it needs.

    Mule 3.2 supports this new “plugin” packaging as well as regular Mule Module JARs.

    The new maven-mule-plugin (which is used to package apps) can also be used to package modules and generate plugins.

  3. Regarding polling end-points – yes, the cluster arranges the nodes so that at any given time, only one is polling.

  4. David, yes, there is an election process that occurs among the nodes to decide who polls.

  5. I’m confused as to how you make HTTP reliable without transactions or is the definition of reliable only when a HTTP message is put on an internal JMS Q.

  6. “Reliable”, in the most general sense, means that every input results in the correct output. The reliability patterns for HTTP ensure that one of the following occurs:

    * The HTTP request was received and saved in some transactional store (e.g. JMS or VM). In this case, a success (200-series) status is returned.

    * It was not possible to save the HTTP request. In this case, an error (400 or 500 series) status is returned, alerting the client that the request failed and must be resubmitted.

  7. […] couple of months back we released Mule 3.2.  Mule 3.2 is the version we recommend for all Mule users.  The latest release of Mule 3.2 is […]

  8. […] couple of months back we released Mule 3.2.  Mule 3.2 is the version we recommend for all Mule users.  The latest release of Mule 3.2 is […]

  9. […] Mule Enterprise 3.2 introduced a powerful feature allowing to keep track of everything happening during the lifetime of your applications: Business Event Analyzer. This provides a place to monitor business transactions and events across multiple systems. Most businesses need access to information surrounding the following use case examples: […]