Mule ESB 2.2.8 Enterprise Release

June 21 2011

0 comments 0

I’m pleased to announce the release of the latest and most stable version of Mule ESB for those still using our 2.2.x branch. This fix contains over 40 changes including bug fixes and some cool new features since 2.2.7 EE release. Some of the new features to highlight are

Support for class hierarchy on the exception patterns

Before you had to explicitly define all the exceptions (or pattern that would match them) in the exception-pattern to commit or rollback a transaction. With this enhancement, you can now use your exception class hierarchy to commit or rollback. For example you have the following exception class hierarchy:

If you want to rollback on any InvalidRequestException, on previous versions you had to put in the exception-pattern all exceptions or a pattern that would match them all. Now you can just put InvalidRequestException and all the children classes will match it, as now we check if it’s an instance of. Here is an example on how you can make this work, by adding a ‘+’at the end of the fully qualified exception.

Here you can read more about Error Handling in Mule ESB

Support for Custom JMX Authenticator

Before the JMX Agent only supported simple password authentication coded in the SimplePasswordAuthenticator. Now you can define your own JMX Autheticator on the JMX config like in the example below.

Here you can read more about JMX Management in Mule

Exception Strategy can stop the Service

We added a new property in the default service exception strategy (org.mule.service.DefaultServiceExceptionStrategy) to be able to stop the service to ensure it will not continue processing messages. This is useful in case you want to stop processing messages after a particular exception is thrown (DB server is down for example) to prevent unnecessary load on the se  rver retrying the messages. Once you solved the underlying cause for the exception (start the DB server), you can resume the service through the JMX console. Here is a simple example on how you can achieve this.

Here you can read more about Error Handling in Mule ESB

Caching of JNDI entry for JMS queue location

We added a way to configure the JNDI resolver to use to look for your JMS queue location. Now you have the SimpleJndiNameResolver and the new CachedJndiNameResolver. The cache will store the queue location internally and will not try to resolve it every time the queue location is needed. To read more about this visit the JMS Transport page

Current subscribers can download Mule ESB 2.2.8 Enterprise with Mule ESB Management Console from the MuleSoft customer portal. You can also evaluate the 3.1.2 EE version we released recently with the latest features here.


We'd love to hear your opinion on this post