Enterprise Edition
September 28, 2012
MuleSoft is pleased to announce the release of Mule ESB 3.2.3. This maintenance release for Mule ESB Enterprise and Mule ESB Management Console resolves several issues and includes four improvements. Mule ESB 3.2.3 is available for download to Enterprise customers via our MuleSoft Customer Portal.
September 28, 2012, v1.0 Initial Publication
Novermber 12, 2012, v1.1 Additional items added to Fixed in This Release
| Enterprise Edition | Community Edition | |
|---|---|---|
ESB |
Version 3.2.3 |
|
Mule Management Console |
Version 3.2.3 |
|
This maintenance release focused primarily on resolving issues related to JDBC, HTTP, and SEDA queues. We fixed 65 issues, including over 40 critical issues (refer to Fixed in This Release for details). Further, we made the following four improvements:
-
MULE-5940 - HTTP Transport needs support for PATCH method
-
EE-2839 - Transport: JDBC - Retrieve the count for UPDATE, DELETE, INSERT
-
MULE-6251 - Add a default object store for non internal usages
-
MULE-6405 - Transport: HTTP(S)/Jetty - Transport exception mapping mechanism must extensible
For most use cases, Mule ESB 3.2.3 does not change the hardware and software system requirements established in Mule ESB 3.2.2.
Please contact MuleSoft with any questions you may have about system requirements.
View Resolved Issues
EE-2730 |
In clustered mules, messages with Stream payloads are lost |
MULE-6189 |
Failed to initialise app. MBean Exception. |
MULE-6159 |
Proxy Service fails with NPE when the WSDL has Faults defined |
MULE-6065 |
Adding $\{app.home}/lib to the java.library.path |
EE-2688 |
Add data mapper dependencies to mule standalone distro |
MULE-6398 |
schema attributes with propertyPlaceholderType do not support expressions with nested square brackets |
MULE-6387 |
Exceptions cannot be caught ( RetryPolicyExhaustedException ) |
MULE-6374 |
Session properties lost in an Exception Strategy |
MULE-6370 |
Logging initialization can cause stack overflow for some setups |
MULE-6368 |
TemplateParser parse() supports nested expression evaluators but validate() fails with nesting |
MULE-6366 |
JDBC Outbound endpoint, loss of session properties when outbound endpoint is request response |
MULE-6351 |
Expressions with 2 or more levels of nested square brackets are not parsed correctly |
MULE-6335 |
MEL fails to concatenate strings |
MULE-6329 |
Flow with CXF should be able to return unwrapped exception |
MULE-6325 |
Stateful flag does not work in Quartz endpoints |
MULE-6287 |
ClassCastException when binding interface returns null |
MULE-6285 |
Some transformers create execution contexts that are not cleared after execution |
MULE-6249 |
Custom Exception Strategy class not getting being invoked in a Jetty Inbound Endpoint |
MULE-6248 |
Session variable gets lost if I use an enricher |
MULE-6234 |
Cannot use QueuePersistenceObjectStore on UntilSuccessful |
MULE-6200 |
Binding does not work with dynamic endpoints |
MULE-6171 |
When deploying a flow that has a mule-config.xml with a future date, it starts a boucle of deployments |
MULE-6102 |
VM Queue not picking up messages previously persisted in the questore directly |
MULE-6069 |
Email transport makes infinite copies of messages |
MULE-6058 |
Cannot override the JsonTransformerResolver |
MULE-5997 |
Inconsistent definition of some expression evaluators |
MULE-5965 |
Mule throws EOFException when it finds an empty message within a queue store |
MULE-5942 |
Content-Encoding header not set correctly when using gzip-compress-transformer with http:outbound-endpoint |
MULE-5940 |
HTTP Transport has no support for PATCH method |
MULE-5860 |
Inserting <collection-splitter /><collection-aggregator /> into a flow produces unexpected results |
MULE-5852 |
request-reply router does not preserve session properties |
MULE-5776 |
Jetty and Ajax transport do not extend correct schema type and are therefore missing various configuration options |
MULE-5534 |
CLONE - Message modifications are discarded when using Collection Aggregator |
MULE-4634 |
UnsupportedEncodingException "utf-8" since java 1.6.0.1x |
MULE-4213 |
Response transformer results are discarded when using multicasting router |
EE-2724 |
Batch update forces Map payload when that is not needed |
EE-2839 |
Retrieve the count for UPDATE, DELETE, INSERT |
MULE-6363 |
Applications are not being disposed on deployment failure |
MULE-6352 |
TemplateParser doesn’t replace expressions resulting in null |
MULE-6346 |
SpringBeanLookup.getObjectClass() is not idempotent |
MULE-6341 |
Remove flakiness in FileEncodingFunctionalTestCase |
MULE-6289 |
Mule Context missing when receiving a message on TCP inbound endpoint |
MULE-6198 |
Do not append / to the URL if path already has the leading / |
MULE-6131 |
Defect in TemplateParser when using a Groovy Expression containing pipes |
MULE-5825 |
JDBC DataStore requires that the JDBCConnector has the queryTimeout set to work |
EE-2657 |
Cannot reference JDBC Datasources using JDBC EE schema |
EE-2658 |
Cannot reference JDBC Object Store using JDBC EE schema |
MULE-6236 |
Unable to set content-type on RestServiceWrapper |
MULE-6082 |
Application Deployment Descriptor is not properly closed |
MULE-6068 |
LocalURIResolver for XSLTTransformer won’t resolve relative paths |
MULE-5870 |
WSProxyService throws exception using Flows (but not Services) when a message is received. |
MULE-6257 |
commponent takes only one "m" |
MULE-6251 |
Add a default object store for non internal usages |
MULE-6240 |
TransactionalQueueManager loads all keys from all ListableObjectStores in order to populate internal message queues |
EE-2681 |
recover() method in TransactionalQueueManager should check for empty keySet from object store |
EE-2737 |
Mule should not use default user exposed object store for internal purposes. |
MULE-6403 |
IdempotentRedeliveryPolicy is not thread safe |
MULE-6400 |
IdempotentRedeliveryPolicy does not rely on Mule object store manager to create an object store |
MULE-6388 |
WS Proxy does not support parameters or XSDs |
MULE-6360 |
Spring 3.x default properties broken in Mule |
MULE-6056 |
SFTP Transport sets property filename on inbound and does not apply outputPattern on outbound if filename is set |
MULE-5998 |
As from 3.2 aggregators no longer maintain the order events are received when creating MuleMessageCollection |
EE-2674 |
JMS Consumer fails in HA Cluster |
EE-2770 |
Only the primary node should subscribe to a topic |
MULE-6079 |
IdempotentMessageFilter can process a given message multiple times |
MULE-6405 |
Transport exception mapping mechanism is not extensible |
MULE-6173 |
Transformer weighting algorithm fails to determine transformer with higher priority |
MULE-6032 |
Mule 3.2.1 HTTPS outbound endpoint leaking file descriptors |
MULE-5389 |
Jersey Resources Components do not support interface binding |
MULE-5104 |
Mule3 Notifications are not fired |
MULE-6019 |
Transactions on one-way vm queues causes CPU to go warm |
EE-2552 |
WMQ Native Transport - Leak in the Output Connections lead to an error when having high number of concurrent request |
EE-2798 |
Backport support for Cluster aware MessageSource in 3.2.x branch |
MULE-6183 |
DynamicOutboundEndpoint.createStaticEndpoint is marked as synchronized and causes congestion under high load |
The improvements and fixes that Mule ESB 3.2.3 introduces require no specific migration activities for Mule ESB and Management Console.
For more details on how to migrate from previous versions of Mule ESB, access the library of Migration Guides.
Please refer to the following resources for assistance using Mule ESB 3.2.3.
Refer to Mulesoft.org for Mule ESB 3.2.x reference materials.
Access MuleSoft’s MuleForge forum to pose questions and get help from Mule’s broad community of users.
To access MuleSoft’s expert support team, subscribe to Mule ESB Enterprise Edition and log in to MuleSoft’s Customer Portal.