Version: 3.4.2
Build: 5ccc2ab60c
Mule ESB 3.4.2 Release Notes
January 6, 2014
MuleSoft is pleased to announce the release of Mule ESB 3.4.2 which offers fixes for issues and improvements to the core Mule ESB product and the Mule Management Console.
These release notes apply to the core changes we have applied in 3.4.2 runtime, and to the Mule Management Console, both of which are available to Enterprise customers. Access one of the following resources to download Mule ESB 3.4.2 Enterprise runtime and take advantage of an improved and hardened Mule ESB.
-
Download Mule 3.4.2 standalone and the latest version of the Mule Management Console from the MuleSoft Enterprise Customer Portal.
Current Release Version
Enterprise | Community | |
---|---|---|
ESB |
Version: 3.4.2 |
n/a |
Management Console |
n/a |
|
Management Console |
Version: 3.4.2 |
n/a |
Noteworthy
-
Management Console Installation or Upgrade: Depending on your requirements and current instance of MMC, you require one of two .
war
files to install or upgrade MMC. -
Management Console improvement: We have made it easier to persist state and tracking data to an external database, requiring only a couple of property files and minor XML configurations in almost all cases.
-
Management Console improvement: Out of the box, MMC now includes the ability to encrypt passwords in order to connect to the state and tracking databases and to bind to LDAP.
-
Management Console improvement: We have greatly improved both the performance of business events and the functionality of queries.
Hardware and Software System Requirements
For most use cases, Mule ESB 3.4.2 does not change the hardware and software system requirements established by Mule ESB 3.4.1. Contact MuleSoft with any questions you may have about system requirements.
Important Notes and Known Issues in this Release
This list covers some of the known issues with Mule Management Console 3.4.2. Please read this list before reporting any issues you may have spotted. (There are no known issues with Mule ESB 3.4.2 Enterprise Runtime.)
Mule Management Console
Adding a cluster to a group |
If you place a cluster in a server group, you may experience issues with deployments which target the group instead of the cluster directly. |
Adding a server to a group |
If you add a server to a group via the server details panel (using the settings tab and editing the server info), deployments targeting the group are not transferred to the newly added server. |
Error Messages |
Some error messages in the MMC main window may contain a "See More" link which, when clicked, displays a new window containing only the text |
Fixed in this Release
Mule ESB
View resolved issues
Issue | Description |
---|---|
EE-2916 |
java.io.NotSerializableException at org.mule.config.spring.parsers.assembly.MapEntryCombiner when having a JDBC Inbound in a clustered environment |
EE-3322 |
ClassCastException using inbound file endpoint in cluster |
EE-3327 |
Add property to disable MMC agent to wrapper.conf |
EE-3344 |
populatem2repo script does not include mmc related jars |
EE-3394 |
Populate M2 Repo does not populate Clover |
EE-3449 |
Incorrect validation for node ID in cluster causes error on removal if node IDs are not reassigned |
EE-3470 |
Queues with limited size behave differently in standalone and cluster mode |
EE-3473 |
The generated Studio runtime bundle needs to have a different internal structure |
EE-3475 |
Update assembly allowlist to support latest clover-version |
EE-3496 |
Expensive lookup in Spring Registry is performed every time a MEL expression is evaluated |
EE-3535 |
Change MVEL dependency to use mule’s MVEL |
MULE-6577 |
Failure to propagate the correlation ID across JMS queues |
MULE-6800 |
Thread leak on Mule redeployments for embedded |
MULE-6831 |
Applications deleted when deployment fails |
MULE-6908 |
Property place holders should be supported in test conectivity |
MULE-6918 |
Add dynamic round robin routing support |
MULE-6920 |
Race condition on startup of Mule Context |
MULE-6959 |
Race condition creating MVELExpressionLanguage instances |
MULE-6965 |
Error during mule message serialization when using byte array as payload |
MULE-6968 |
Http endpoint with path="" or path="/" do not attend requests at root level |
MULE-6969 |
InputStream not closed on Scriptable |
MULE-6988 |
The Jetty transport does not have an option to configure the number of acceptor threads |
MULE-6989 |
Quartz synchronous is not using the configured exception strategy |
MULE-6990 |
OOM exception using foreach |
MULE-6993 |
ClassCast exception when using cxf:proxy-service and validationEnabled, and the request contains a CDATA field. |
MULE-6995 |
DynamicOutboundEndpoint does not use the connector’s service overrides |
MULE-6997 |
Rollback Exception Strategy retries an incorrect number of times |
MULE-6999 |
File Transport delays the processing of files when pollingFrequency attribute is uncomfortably narrow |
MULE-7005 |
ServerNotification completing work after listener failure |
MULE-7008 |
Private flow sends duplicate message when replyTo property is set |
MULE-7012 |
HTTP/HTTPS outbound endpoints ignore the keep-alive attribute |
MULE-7015 |
ObjectToHttpClientMethodRequest fails to process DefaultMessageCollection when http.version is set to 1.0 |
MULE-7025 |
Serialization exception using persistent queues |
MULE-7027 |
ExpiringGroupMonitoringThread must process event groups only when the node is primary |
MULE-7028 |
MuleMessageToHttpResponse not evaluating outbound scope to set the content type header |
MULE-7034 |
MuleEvent is not serializable when using a JDBC inbound endpoint with a nested query |
MULE-7036 |
QueuedAsynchronousProcessingStrategy ignores queue store configuration |
MULE-7040 |
Request-reply throwing ResponseTimeoutException on Mule shutdown |
MULE-7041 |
EventProcessingThread must manage exceptions thrown by implementation classes |
MULE-7042 |
Event correlation timeout incorrectly detected on cluster |
MULE-7050 |
MuleApplicationClassLoader loadClass() method not synchronized |
MULE-7055 |
PersistentObjectStorePartition throws ObjectDoesNotExistException with a null message |
MULE-7062 |
It is not possible to send outbound attachments over http |
MULE-7080 |
Race condition checking file attributes on SFTP transport |
MULE-7087 |
NullSessionHandler - Empty Mule Session header |
MULE-7088 |
Improve the way Mime types are registered for outbound http attachments |
MULE-7096 |
Performance problem accessing Spring Registry every time a MEL expression is evaluated |
MULE-7110 |
Improve JMS transport to support reconnection at the endpoint level |
MULE-7114 |
Outbound HTTP Patch call is not sending the payload as message body |
MULE-7116 |
Message receiver fail when trying to schedule work after reconnection |
MULE-7118 |
Incompatible usage of MVEL on Drools |
MULE-7125 |
requireClientAuthentication="true" not working on jetty SSL connector |
MULE-7144 |
Differentiate TCP connection timeout from responseTimeout |
MULE-7148 |
Differentiate HTTP connection timeout from responseTimeout |
MULE-7153 |
JMS Queue - CXF Service failing in 3.4.1 EE, working in 3.4.0 EE |
MULE-7155 |
Add appending support to the SFTP transport |
MULE-7165 |
Request Body is not closed in the HttpMessageReceiver |
Mule Management Console
Issue | Description |
---|---|
MMC-1521 |
Reduce number of operations in the deployment process |
MMC-1523 |
Streamline externalization of persistence into PostgresSQL and other DBs |
MMC-1526 |
Allow to view more events on BE page in Webapp |
MMC-1546 |
Improve business events filter behavior for complex queries |
MMC-1547 |
New Cluster option disabled when it shouldn’t |
MMC-1555 |
Add SQL Server support and instructions for MMC state data and BE |
MMC-1560 |
Provide feedback link is broken |
MMC-1561 |
Support link is broken |
MMC-1572 |
Create separate 3.4.2 war file with MS SQL Server support |
MMC-1575 |
Business events persist mechanism needs to be updated to new mapping and get concurrency improved |
MMC-1576 |
Reduce load of repetitive queries from business events |
MMC-1578 |
Business events - events tab should also have paging |
MMC-1583 |
Optimize indexing strategy for business event tables |
MMC-1584 |
Improve business events caching mechanism, remove unnecessary caches |
MMC-1597 |
When adding search filters, take less time to show the available options |
MMC-1598 |
Fix removal of node from cluster when node ids are not in sequence |
MMC-1600 |
Typo in button - "Applies changes" should be "Apply changes" |
MMC-1609 |
Add comments in database / LDAP configuration properties files |
MMC-1610 |
Encrypt passwords in database |
MMC-1611 |
Externalize db query for cleanup script |
MMC-1613 |
Make sure all external links open in a new browser tab |
MMC-1619 |
Create KB article and groovy script to address MS-SQL issues with Cleanup Script |
MMC-1643 |
User with only monitor rights has issues accessing all information if there’s a cluster defined |
MMC-1667 |
Externalize combo population query |
MMC-1666 |
Upgrade to OpenJPA 2.3.0 |
SE-32 |
Improve LDAP configuration security |
SE-170 |
Business Events limited to 1000 results |
SE-373 |
SQL Exception is thrown when Tracking Cleanup script is executed on MySQL Tables |
SE-477 |
MMC switches tabs when selecting the log folder |
Third Party Connectors and other Modules
At this time, not all of the third party modules you may have been using with previous versions of Mule ESB have been upgraded to work with Mule ESB 3.4.2. Contact MuleSoft if you have a question about a specific module.
The following library has been upgraded with Mule ESB 3.4.2:
-
Java Secure Channel (JSch) 0.1.50
Migrating from Mule ESB 3.4.1 to 3.4.2
The improvements and fixes that Mule ESB 3.4.2 introduces require no specific migration activities for Mule ESB or Mule Management Console.
Support Resources
Refer to the following resources for assistance using Mule ESB 3.4.2.
-
Access MMC 3.4 docs.