Dreamforce On-Demand

Mule ESB 3.2.0 Release Notes

The Mule team is proud to announce the release of Mule 3.2 Enterprise, the most stable and reliable version of Mule with radically more powerful capabilities for reliability and visibility

Current Release Version

Enterprise Edition

Community Edition

ESB

x

Management
Console

x

Feature Highlights:

Request-Reply messaging style for Flows
Tighter control over Flows
Improvements in transactional behavior
Better performance through SEDA queues
Drools support added
Fine-grained class loading control and plugin packaging
New "Retry Until Successful" message processor
Simplified data-source configuration for JDBC transport
High Availability Clustering (EE) Enterprise Edition
Business Event Analyzer (EE) Enterprise Edition
More REST APIs for Management (EE) Enterprise Edition

Important notes for this release

The default rules for how a Mule flow is processed have been made more consistent, and configurations have been given the ability to override these defaults:
- A Mule flow that is not transactional and whose inbound endpoint uses the one-way exchange pattern will, by default, use a SEDA queue and be processed asynchronously.
- A Mule flow that is either transactional or whose inbound endpoint uses the request-response exchange pattern will, by default,be processed synchronously.
- These defaults can be overridden with a new construct called a Processing Strategy. See Flow Processing Strategies for information on this.
- Processing strategies also allow the details of threading to be configured. Thus, the threading-profile element is no longer supported on flows.
Request Reply messaging style has been added to flows. This messaging style is well suited for scenarios where you want to send a request that results in an asynchronous reply message.

Limitations

Currently a Mule HA Cluster supports up to 4 nodes per Cluster
Nodes within a mule cluster nodes are intended to run each on on a separate psychical/virtual machine.
Currently, the Until-Successful router, which will retry an operation until it succeeds, will retry it only on one node of a cluster.

Known Issues

Two of the schema references in the configuration file for the mmc application in the ESB Enterprise v3.2 trial download point to 3.1 locations. This can cause problems in starting the server. To fix the issue, open the configuration file (<mule>/apps/mmc/mule-config.xml) and
make the following updates:
When using the Mule ESB Enterprise management console in the EE bundle the mule instance cannot be used as a cluster node. When managing clusters it is recommended that the management console be installed in a web container such as Apache Tomcat.
Currently if two nodes of a four nodes cluster go down simultaneously, there can be a possibility of losing messages. This will be addressed in a future release.
Due to a bug in ActiveMQ, when requesting for an event more than one time from a transactional endpoint within the same transaction, the second request will return always null, or hang if no timeout is used.

Migration

For further information on migrating from Mule 3.1.x to 3.2 see the migration topic.

Bug Fixes in this release:

JIRA Issues (131 issues)

Priority

Type

Key

Summary

Blocker

WebAppClassLoader causes StackOverflowError within ApplicationAwareRepositorySelector

Blocker

Transport Archetype: Tests fail from Maven

Blocker

Stack overflow caused when Jetty initializes it’s logging subsystem (e.g. when deploying/touching mule-config.xml to trigger redeployment of the bookstore example)

Blocker

Element socketFactoryProperties does not have an associated Bean Definition Parser

Blocker

The UDP inbound sends a response back even though the exchange pattern is set to one-way

Blocker

Starting a stopped Async service results in the service NOT consuming any messages

Blocker

mule-jms.xsd fails schema validation

Blocker

Mule won’t launch with space in path

Blocker

loanbroker-simple example’s README.txt has a dead link

Blocker

Tests "test[archetype name" fail OOTB for Module, Example, Catalog and Project Archetypes]

Blocker

In the bookstore example, the expected recipient doesn’t receive email; the sender receives the email instead

Blocker

Mistake in the online docs of the Security example

Blocker

WebsphereTransactedJmsMessageReceiver.doConnect() does not call super.doConnect(), so XaTransactedJmsMessageReceiver.redeliveryHandler is not set

Blocker

Mule examples launcher fails to build with maven

Blocker

Some examples don’t work in example launcher application.

Blocker

GPS Walker Example does not run in Internet Explorer 8

Blocker

Twitter page displays an old supported Mule Version

Blocker

Idempotent filter fails in a cluster

Blocker

When configuring <default-exception-strategy> inbound transaction is committed by default when no commit or rollback pattern is configured

Blocker

Studio needs a way to indicate what Mule version a config was created for

Blocker

Sub-flows (and processors defined in them) don’t get muleContext injected or lifecycle when used via flow-ref

Blocker

IllegalStateException when shutting down a connector

Blocker

Patch submission

AbstractSplitter should process elements lazily

Blocker

Attribute (reverseOrder) in xsd, has no field equivalent in FileConnector

Blocker

Issue with quartz storing information in a jdbc data store because of a bug in quartz 1.6.0 which is fixed in 1.6.6

Blocker

Parsing Simple Component elements causes an NPE if they contain more than one attribute

Blocker

jcifs v1.3 can’t be found in repos anymore, blocks a clean build

Blocker

HTTP NTLM Proxy authentication doesn’t work

Blocker

Messages may be sent to the wrong one when using dynamic endpoint

Blocker

"default-service-exception-strategy" is permitted in flows

Blocker

Examples Launcher - CEP example - "Run it tab" - Link to docs is wrong

Blocker

Patch submission

Content-Type header not set with PUT method

Blocker

WebService frontend in mule, doesn’t return Business exception which is in contract of method

Blocker

FTP connector should not change working directory if Path is empty

Blocker

PDF version of the "Mule ESB 3 User Guide" contains null pointer exceptions

Blocker

CXF interceptors get shared across applications which creates unexpected errors

Blocker

In the example-launcher example. link in the README.txt points to a page which says "You cannot view this page due to inherited restrictions"

Blocker

Repackage bookstore app to use standard <jetty:webapp/> facilities

Blocker

Switch to Java 6 baseline

Blocker

Secure echo does not work in Notifications example

Blocker

WS-Addressing when used causes a NPE

Blocker

Monitored object store throwing a warning of not finding elements after first call to idempotent filter in clustered environment

Blocker

Polling receivers use wrong classloader when running in Mule standalone

Blocker

Old documentation

Blocker

Blocker

CXF jaxws-client fails with HTTP input

Blocker

Remove Acegi module

Blocker

Drop backport-util-concurrent in favor of native Java 6 concurrency building blocks

Critical

No information displayed for some transformers due to type attribute missing from schema - XSLT not detecting inheritance

Critical

TCP outbound-endpoint performance is poor

Critical

Components cannot be used in globally defined sub-flows or processor-chains

Critical

When configuring <default-exception-strategy> exception message is no longer routes to nested processor/endpoint unless configured to commit

Critical

Flows does not handle exception when invoked via i) request-response vm inbound endpoint ii) flow-ref

Critical

Support non-endpoint message sources

Critical

Custom transports fail to load when bundled in a Mule app (vs deployed in Mule system libs)

Critical

testFlowRef() in FlowConfigurationFunctionalTestCase passes but the expected payload should be "012xyzabc312xyzabc3" not "012xyzabc3"

Critical

Problems when using JMS with LDAP

Critical

Per-app log files

Critical

CXF proxy does not propagate root cause of an exception.

Critical

Schema issue - Incorrect Inheritance for Transformer Reference

Critical

JMS Reconnection fails due to inconsistent connector lifecycle state

Critical

Make it easier to understand startup progress in the mule console

Critical

Quartz: If running a job which was stored in a database the muleContext is no longer valid and thus the context should be retrieved from the quartz connector

Critical

Invoker MessageProcessor does not work with zero arguments

Critical

Decouple flow synchronicity with endpoint exchange pattern and transactionality

Critical

Mule cxf endpoint is not able to call SOAP 1.2 webservice

Critical

By default the exchange pattern in the dynamic endpoints is null

Critical

Upgrade Jersey (and client) to 1.6

Critical

returnSourceIfNull in expression-transformer is not working for scripting evaluators

Critical

Problem using splitter in flow for 3.1

Critical

Quartz jobs in separate Mule apps interfere

Critical

Patch submission

cxf:jaxws-service mtomEnabled doesn’t work

Critical

Static recipient list router not able to bind transactions

Major

Upgrade Quartz dependency

Major

Creating a config file with eight (8) <collection-aggregator-router>s prevents mule from completing startup sequence

Major

Log File Per App - support log4j.xml configs

Major

Errorhandler example distribution build fails (mvn-ant)

Major

Reload log4j configs on the fly

Major

Automatic response when sending message to a queue

Major

There is no option to include the documentation module when creating an archetype in Mvn

Major

HTTP throwing "Property "cookieSpec" has an incorrect or unsupported value "rfc2109"" error while the schema admits this value

Major

configuration-ref is displayed twice in the mule-cxf schema and the way you can use it makes Mule fail

Major

Patch submission

Add support for global namespaces in the XPathExtractor

Major

IOException when redeploying a project

Major

Schema inconsistencies - File connector contains transaction options because of schema inheritance

Major

Weblogic JMS transport, error in the reconnection to JMS

Major

Bundle jsp support for <jetty:webapp/> config element

Major

FTP message requester does not delete files

Major

Single-app option (-app) doesn’t explode zips, works only with exploded apps

Major

localhost means something different on the Jetty connector compared with all other mule socket connectors

Major

<message-filter throwOnUnaccepted="true"> does not work for endpoints with exchange pattern request-response

Major

Service exception strategy should be able to stop the endpoint receivers

Major

Sybase Stored procedure/queries does not correctly manage column aliases

Major

Using dynamic endpoint produce error when using async response

Major

Reloadable message resource bundles

Major

Remove transport part of the RSS module

Major

Distribution example zips contain a timestamp in the name

Major

CXF Proxy - no faultstring returned

Major

TcpConnector uses its own socketsPool and effectively ignores <threading-profile..> so only one dispatcher socket available by connector

Major

Simplify JDBC data source and connection pool configuration

Major

custom-security-filter should allow setting properties and referencing a bean

Major

Remove transport part of the Atom module

Major

Generic authentication interceptor

Major

Example app to illustrate using a Rules Engine with Mule

Major

Add Until Successful message processor

Major

Support for a Rules Engine in Mule

Major

CEP example cannot be undeployed completely

Minor

mule-tools-anttasks ended up in lib/opt, must be in lib/mule

Minor

When using test component, it would be useful to be able to specify an Exception message.

Minor

MuleEvent.getEndpoint() endpoint type is ambiguous

Minor

idempotent-receiver-router does not allow custom object store in XML configuration

Minor

IMAP Connector throw an NPE Exception if property deleteReadMessages="false"

Minor

Broken links in bookstore example web page

Minor

mule-atom.xsd fails schema validation

Minor

mule-rss.xsd fails schema validation

Minor

SMTP endpoints don’t use expression evaluator

Minor

Add sequence router

Minor

The assembly plugin is not included in the POMs of the Transport, Module, Example, and Catalog archetypes

Minor

Allow HTTP endpoints to serve static content such as html, css, javascript

Minor

xpath-node evaluator throws an exception if the input type is org.w3c.dom.Document

Minor

Patch submission

Allow Pattern flags in RegExFilter

Minor

per-app logging: main mule logger does not log when an app deployment is complete

Minor

Invalid application zip is detected as a new application

Minor

Make JmxAuthenticator configurable for JMX remote management

Minor

When using a single-app option (-app) container start-up message is not printed to the system log

Minor

Upgrade Jackson to 1.8.0

Minor

Consider dropping or recalculating "Content-Length" header if a transformer is used on ws:proxy

Minor

mule-module-drools is in lib/opt, should be in lib/mule

Trivial

Https transport documents acegi security filter

Trivial

Startup console feedback improvements

Trivial

Add FileSize to message property