Mule ESB 3.6.1 Release Notes
March 3, 2015
MuleSoft is pleased to announce the release of the 3.6.1 Runtime.
Current Release Versions
| Enterprise Runtime | |
|---|---|
ESB Runtime |
Version: 3.6.1 |
Anypoint Studio |
Version: January 2015 |
MMC |
Version: 3.6.0 |
Anypoint DevKit |
Version: 3.5.2 and later |
APIkit |
Version: 1.6.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.
| Mule ESB 3.6.n uses log4j2. Ensure that you’re using the latest logging configuration. |
HTTP Connector Security Issue
This release fixes the HTTP Connector security issue described in this release bulletin.
Fixed Issues
Using set-variable does not removes variables when assigned value is null |
|
Undeployment does NOT release pooled database connections |
|
HTTP Listener doesn’t validate clients |
|
Client credentials does not fail if it could not retrieve access token |
|
HTTP static resource component fails with HTTP listener |
|
Add support for bulk updates using dynamic queries |
|
HTTP Listener does not handle "Expect: 100-Continue" (RFC 2616) header correctly |
|
OAuth2 postAuthorize() with an expired token fails even if token was refreshed |
|
Simple HTTP Proxy with > 1k payload incremente latency 1000x |
|
HttpRequester not configuring TLS cipher suites and protocols |
|
Mule 3.6 HTTPS Request Connector does not validate certificate presented by remote server |
|
Support TLS SNI Extension in Http OutboundEndpoint |
|
Mule global log config is not found when application has plugins |
|
Comparator not finding the class in the right classloader |
|
Avoid to set the same message listener on the message consumer |
|
The changes in MULE-7742 impacted in performance, a better solution should be used. |
|
OAuth authentication code doesn’t fail when access token is null |
|
SFTP inbound-endpoint autoDelete="false" does not work |
|
Supported and recommended JRE version should be at least 1.7.0_60 |
|
Endpoint notifications problem when using CXF |
|
Core extension dependencies are not initialized in order |
|
SftpMessageReceiver doesn’t release the lock on files |
|
SFTP connect hangs in pre-authenticated phase |
|
Build number Maven plugin should be activated always |
|
Inconsistent implementation of streamingMode="NEVER" between listener and requestor. |
|
Exception in HTTP listener when path="/" and basePath="/" |
|
Change DB connector resultsets to TYPE_FORWARD_ONLY to support additional databases |
|
Outbound endpoints should be correctly disposed when an app with shared resources is undeployed or redeployed. |
|
Mule starts when a request element has host/port undefined, only failing when request is used. |
|
HttpListener ParameterMap should behave as a Map |
|
Fix DateTimeTimeTestCase.seconds flakyness. |
|
Setting encoding attribute on a transformer has no effect |
|
Upgrade Commons File Upload |
|
Upgrade HTTP Client |
|
Disable/Remove Alert Definition from MMC agent does not stop the alert from firing |
Hardware and Software System Requirements
For most use cases, 3.6.1 Runtime does not change the hardware and software system requirements established by the 3.6.0 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.