Mule ESB 3.6.2 Release Notes
April 15, 2015
MuleSoft is pleased to announce the release of the 3.6.2 Runtime.
Compatibility Information
| Software | Version |
|---|---|
ESB Runtime |
3.6.2 |
Anypoint Studio |
|
MMC |
|
Anypoint DevKit |
|
APIkit |
1.6.0 and later |
| In case of having any issues with APIKit, consider the upgrading to the latest minor release of APIKit. |
Features
-
JRuby 1.7.4 or later support.
-
Spring 3.2.13 or later support - This includes these JAR files: spring-aop, spring-beans, spring-context, spring-context-support, spring-core, spring-expression, spring-jdbc, spring-jms, spring-tx, spring-web, spring-webmvc.
-
Tomcat Libraries 6.0.41 support.
-
HTTP connector security issue fixed.
Notes:
-
Mule ESB 3.6.n uses log4j2. Ensure that you’re using the latest logging configuration.
-
See MMC 3.6.2 Fixes for MMC update changes.
Enterprise Edition Fixed Issues
| Issue | Summary |
|---|---|
EE-4333 |
Removed Axis Transport from ESB Distribution |
EE-4332 |
Make MuleContext available in HazelcastInstance |
EE-4330 |
EE distribution uses validation-api-1.0.0-GA.jar instead of validation-api-1.0.0-final.jar |
Community Edition Fixes
| Issue | Summary |
|---|---|
MULE-8370 |
ObjectAlreadyExistsException when using splitter and until-successful |
MULE-8368 |
Modify substitutableInt restriction to allow APIGateway extension language |
MULE-8367 |
Add http.relative.path to the list of inboundProperties in the new HTTP module |
MULE-8365 |
JSON validate-schema doesn’t pick up a schema if it is in an application’s classpath |
MULE-8362 |
Update Spring-AOP to version 3.2.13 or greater |
MULE-8361 |
Race condition in ExpressionConfig |
MULE-8349 |
Incorrect anchor file content |
MULE-8340 |
HTTPS connectors interfere with each other |
MULE-8338 |
HTTP listener fails when receiving empty request with content type x-www-form-urlencoded |
MULE-8315 |
Upgrade Tomcat libraries |
MULE-8311 |
Schema locations for includes are not being fixed |
MULE-8310 |
FTP client not timing out |
MULE-8308 |
Upgrade JRuby to 1.6.5 or later |
MULE-8306 |
DB Drivers should be removed from DriverManager when MuleApplicationClassLoader is disposed |
MULE-8305 |
ObjectToHttpClientMethodRequest ignoring filename on file attachments |
MULE-8304 |
It is not possible to define more than one keystore/truststore |
MULE-8303 |
ClassCastException when setting a MEL expression in the config-ref of a Connector’s call |
MULE-8300 |
Using set-variable does not removes variables when assigned value is null |
MULE-8184 |
HTTP Listener Server should return method not supported |
Hardware and Software System Requirements
MuleSoft recommends a minimum of 4 GB RAM on a developer workstation. As applications become complex, consider adding more RAM. You can 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.
MMC 3.6.2 Fixes
The following issues were fixed for MMC 3.6.2:
| Issue | Description |
|---|---|
MMC-1814 |
Anchor file not deleted using MMC REST API |
MMC-1807 |
Mule Management Console Bundle doesn’t come with Mule Server registered |
MMC-1806 |
MMC is not showing the correct status of an application |
MMC-1791 |
Events Received Graph (Async): Too specific time scale for clustered application |