Mule ESB 3.5.2 Release Notes
October 14, 2014
MuleSoft is pleased to announce the release of the 3.5.2 Runtime.
Current Release Versions
Enterprise Runtime | |
---|---|
ESB Runtime |
Version: 3.5.2 |
Anypoint Studio |
Version: October 2014 |
Anypoint DevKit |
Version: 3.5.2 |
APIkit |
Version: 1.5.0 |
SAP Connector |
Version: 2.2.4 |
In case of having any issues with APIkit, consider the upgrading to the latest minor release of APIkit. |
New or Fixed in This Release
This release is a maintenance release, and hence doesn’t include any new features and very few minor improvements. Most of the differences between this version and the previous are bug fixes.
Improvements
MULE-7808 |
Upgrade Xalan to version 2.7.2 |
MULE-7805 |
Upgrade Spring version to 3.2.10 in Mule 3.5.x |
MULE-7703 |
Add a way to configure default threading profile |
MULE-7620 |
Define unified way to define the exception handler in execution scopes in mule |
MULE-7599 |
Add GPG signature to artifacts |
MULE-7207 |
Create Scatter-Gather component for parallel multicasting |
EE-4150 |
Solve license checker for CI concern |
Fixed Issues
MULE-7893 |
Avoid endpoint caching ad infinitum |
MULE-7892 |
Enable testing mode in functional tests |
MULE-7887 |
DEPLOYMENT_FAILED status should be applied to applications that fail to start |
MULE-7886 |
Transaction Journal fails to be recovered if queue name has more than 128 charaters |
MULE-7883 |
Wrong wsdl:import definition in exposed WSDL |
MULE-7881 |
Errors thrown during message processor execution are not properly managed |
MULE-7879 |
DB Connector: Missing support to call Oracle function that returns a CURSOR |
MULE-7877 |
Web Service Consumer cannot handle WSDL that import other wsdl that overrides namespace |
MULE-7851 |
SecretKeyEncryptionStrategy does not use the supplied key |
MULE-7828 |
Missing initial multi-part boundary at org.mule.transport.http.multipart.MultiPartInputStream.parse(MultiPartInputStream.java:357) |
MULE-7819 |
GlobalFunctions lead to memory leaks |
MULE-7817 |
ClassLoader leak due to wrong use of DEFAULT_THREADING_PROFILE |
MULE-7814 |
OutOfMemoryError with Jersey/HTTP Streaming |
MULE-7812 |
StaticResourceMessageProcessor holds on to file locks. |
MULE-7804 |
Mule adds an empty inbound property when receiving an HTTP request with an empty query string |
MULE-7803 |
Thread leak on inbound HTTP connections |
MULE-7800 |
Deployment service does not update app status after deployment failure |
MULE-7797 |
ArrayIndexOutOfBoundsException when mixing the order of in/out parameters in DB module. |
MULE-7796 |
IllegalArgumentException when trying to load external query |
MULE-7795 |
File transport being recursive even with recursive="false" in 3.5.1 |
MULE-7778 |
PGP module is unable to decrypt signed files |
MULE-7774 |
Wrong format for date in HTTP header |
MULE-7745 |
Can’t log SOAP Messages |
MULE-7729 |
Possible deadlock when handling concurrent requests in a transaction with more than one outbound endpoint |
MULE-7726 |
No transacted DB connector requires a connection per operation |
MULE-7709 |
mule-db.xsd in mule-module-db-3.5.0.jar refers to mule.xsd version3.4 |
MULE-7708 |
Database: Oracle Configuration still requires user and password attributes when it is configured via spring-bean |
MULE-7704 |
DB connector fails to create a pooled connection when DB driver is deployed in the mule application |
MULE-7697 |
com.arjuna.ats.arjuna.exceptions.ObjectStoreException when executen esireferenceimplementation on windows |
MULE-7677 |
Mule fails to process all files when streaming="true" |
MULE-7674 |
mule frezes with 100% CPU utilization if accessing property of non-existing property |
MULE-7673 |
DatabaseMuleArtifactTestCase broken after maven changes |
MULE-7633 |
MuleBaseVariableResolverFactory cannot assume that nextFactory.getVariableResolver() will return null if variables doesn’t exist. |
MULE-7624 |
Fix JMX agent tests in management module |
MULE-7616 |
Mule should not print the full message on fatal exception |
MULE-7502 |
Exception thrown by one-way outbound endpont in a Catch ES causes infinite loop |
MULE-6839 |
Inbound HTTP Cookies are not available in a Jersey Service Class |
MULE-6622 |
schemaLocation in Message Validation. Mule fails to load an imported second schema |
MULE-6501 |
XsltTransformer forcefully evaluate expressions in context-property into Strings |
EE-4119 |
Clustering module fails to compile on CloudBees |
EE-4079 |
No stack trace when batch logs a non-Mule exception |
EE-4078 |
Batch throws NPE when a step uses a filter to stop a record |
EE-4077 |
unconsistent behavior when using an AbstractMessageTransformer in batch |
Hardware and Software System Requirements
For most use cases, 3.5.2 Runtime does not change the hardware and software system requirements established by the 3.5.1 Runtime. MuleSoft recommends a minimum of 4 GB RAM on a developer workstation. As applications become complex, consider adding more RAM. Please contact MuleSoft with any questions you may have about system requirements.
Migration Guide
For a full and detailed list of considerations when migrating from the previous version to this one, see the MIGRATION.txt
file, located in the root folder of Mule ESB.
Support Resources
-
For details on Anypoint Studio October 2014 release (that comes with 3.5.2 Runtime), see the Anypoint Studio October 2014 Release Notes.
-
Access MuleSoft’s Forum to pose questions and get help from Mule’s broad community of users.