Nav

Mule ESB 2.2.5 Release Notes

Mule Enterprise Version 2.2.5 includes Mule ESB 2.2.5 and the Mule Management Console (see below). This page describes the known and fixed issues in this release.

Current Release Version

Enterprise Edition Community Edition

ESB

x

 

Management
Console

x

 

Management Console

The new version of the Mule ESB Management Console replaces the console formerly known as Mule HQ. While Mule HQ was built on technology from Hyperic, the new version of the console was built from the ground up, reflecting significant feedback from our customers.

Hyperic is optimized for general-purpose monitoring, while the new management console is tightly integrated with Mule ESB and optimized for Mule use cases, including deep Mule-specific diagnostics and auditing capabilities, as well as intelligent alerting for Mule SLAs. The new management console both complements and integrates with open source and commercial monitoring tools, including Hyperic.

To find out more about the Mule Management Console release version 2.2.5, please see the Release Notes and the Mule Management Console Home page.

For an overview of the features and capabilities of the Mule ESB management console, see MMC.

Mule ESB

Mule ESB 2.2.5 now supports hot deployment of web applications to JBoss 4.x, Tomcat 5.5.x and 6.0.x, and Tcat Server 6. It also includes support for IBM JDK 1.5 and 1.6 certification, and it introduces support for a recipient list exception-based router. Last, CXF has been upgraded to version 2.1.9.

Known Issues

This section describes the known issues in this release and, when possible, how to work around each issue.

  • XsltTransformer does not work in Hot Deployment. The XsltTransformer cannot load an xsl file when Mule is deployed in an EAR outside the WAR.

  • Deploying mule-enterprise-jca-jboss-2.2.5 into JBoss 4.2.3.GA shows Incomplete Deployment error. Although this error displays, you can ignore it since Mule is up and running.

  • Tcat Server Console and MMC cannot be hosted on the same tomcat instance. This will be fixed for the GA release.

Fixed Issues

Following is a complete list issues fixed specifically for Mule Enterprise Version 2.2.5

Bug Priority Components Summary

Bug

Blocker

Core: Configuration

Need a mutable threading profile implementation (TP clone)

Bug

Critical

Core: Transformers

When payload is a byte[] msg.getPayload(InputStream.class) should not serialize the payload

Bug

Major

Transport: VM

maxOutstandingMessages attribute ignored on VM queues

Bug

Major

Transport: HTTP/ HTTPS

org.mule.transport.http.transformers.MuleMessageToHttpResponse is not thread-safe

Bug

Trivial

Core: API

Expose ServerNotificationManager’s eventQueue for management

Bug

Major

Core: (other)

MuleSession serialization for 2.2.3+ is not backwards-compatible

Bug

Minor

Core: (other)

FunctionalTestCase does not work without mule-test-exclusions.txt

Bug

Major

Core: Endpoints

EndpointURI password security

Bug

Major

Transport: HTTP/ HTTPS

Incorrect contentType on sync endpoint

Bug

Minor

Core: Configuration

Simplify working with Mule Registry when using a groovy expression evaluator

Bug

Minor

Transport: Email

Mule Email transport and MS Exchange issue

Bug

Critical

Core: API

MuleSession converts all stored property objects to java.lang.String

Bug

Critical

Transport: CXF

Mule CXF proxy service reset http response status to 200 when the backend web service fails

Bug

Minor

Modules: Security (Acegi, PGP, JAAS, others)

Failing unit tests when running the security example from distribution

Bug

Critical

Core: Routing / Filters

Recipient List Exception Based Router

Bug

Critical

Transport: JMS

Memory leak in TransactedPollingJmsMessageReceiver

Bug

Critical

Modules: Security (Acegi, PGP, JAAS, others)

PGP verification fails when strong encryption keys are used

Bug

Blocker

Core: Transformers, Modules: Expressions (OGNL, RegEx, others)

Message property set in the transformer is not available on the second transformer in the same stack

Bug

Critical

Transport: CXF

Message access violation error while using wire-tap-router with cxf endpoint

Bug

Major

Modules: JBoss Transactions, Transport: WebsphereMQ

NullPointerException in org.mule.transport.jms.XaTransactedJmsMessageReceiver

Bug

Major

Core: Configuration

All custom elements should accept spring bean properties

Bug

Blocker

Core: (other)

Storing a non-serializable object to the MuleSession causes an exception in 2.2.3+

Bug

Critical

Modules: MuleClient

Timeout property on MuleClient send sendSync and sendAsyc methods does not work

Bug

Minor

Build: Distributions

Ensure JCA distribution works with current version of Geronimo

Bug

Major

Core: Concurrency / Threading

Possible concurrency issues in TransactionalQueueSession$QueueImpl

Bug

Major

Transport: CXF / XFire

Mule CXF proxy service reset http response status to 200 when the backend web service fails

Improvement

Major

Transport: CXF / XFire, Transport: JMS

No response when attempting to implement sync proxy with cxf over jms

Improvement

Major

Transport: Jetty

JettyHttpsFunctionalTestCase fails

Improvement

Minor

Modules: Management / JMX

Mule should use a platform MBean server by default, not create a new one

Improvement

Minor

Core: Transports, Transport: JMS

ObjectToJMSMessage does not close the InputStream source

Improvement

Major

Core: Configuration

All custom elements should accept spring bean properties

Improvement

Major

Transport: HTTP/ HTTPS

Mule sends Transfer-Encoding header when used with servlet transport, confusing the servlet container

Improvement

Critical

Modules: MuleClient, Transport: CXF / XFire, Transport: HTTP/ HTTPS

MuleClient.send() timeout is not respected with http transport

New Feature

Blocker

Core: API

Enhance Registry API with Map<key,object> lookupByType(Class)