Mule ESB 3.2.1 Release Notes
The Mule team is proud to announce the availability of Mule ESB 3.2.1. This is a follow-up release to Mule ESB 3.2.0, which continues MuleSoft’s commitment to making Mule the industry’s most powerful, complete, and up-to-date enterprise ESB solution.
New in Mule ESB Version 3.2.1
-
Improved cluster performance
-
Enhanced Business Events search usability
-
Custom event details are displayed in-line for improved readability
-
Processing times are now available for out-bound endpoints
-
Limitations
-
Currently, Mule HA Clusters support a maximum of 4 nodes per cluster
-
Each node within a Mule cluster is intended to run on a separate physical/virtual machine
-
Currently, the Until-Successful router retries an operation until the operation succeeds; however, all retry attempts occur on just one node in the cluster
Known Issues
-
The Mule ESB Enterprise Edition trial software cannot be used as a cluster node if you are also using it to evaluate the management console. MuleSoft recommends that you install the management console in a web container such as Apache Tomcat whenever you wish to manage cluster nodes
-
Currently, if two nodes of a four-node cluster go down simultaneously, the possibility of message loss arises. This issue is scheduled for resolution in a future release.
-
Due to a bug in ActiveMQ, whenever a transactional endpoint requests an event more than one time from within the same transaction, the second request always returns "null", if no timeout is used, or it causes the application to hang.
-
This release does not support HP-UX.
-
On occasion, when a cluster is first started it may take up to 30 minutes for all of the required backup memory partition’s to be assigned and active. The state of your backup partition’s can be identified by looking in the logs of any mule instance in the cluster. In cases where this delay occurs, only one partition will be without a backup for this period of time. It is recommended you monitor for this when first starting your cluster in production.
Migration
The "tracking" directory containing data files for the Business Event Analyzer is now placed in the mmc-data directory. If you have been using the Business Event Analyzer with the default database you will need to move the directory called "tracking" into the mmc-data directory. The mmc-data and tracking directories can be found in the working directory of the container running the management console, or under the .mule directory if you are using the trial Mule ESB enterprise edition bundle. Note: if you are using Oracle to store Business Event Analyzer data then no action need be taken.
For information on migrating from Mule 3.1.x to 3.2 see the migration topic.
The following JIRAs are open against this release of Mule ESB:
| Key | Component/s | Summary |
|---|---|---|
MULE-5880 |
Transport: HTTP(S) / Jetty |
AbstractReceiverServlet not allowing to send multiple headers with the same header name |
MULE-5827 |
Core: Endpoints |
File connector in 3.2.0 ignores #[header:originalFilename] and writes no file |
MULE-5781 |
Tools: Archetypes |
Getting NoClassDefFoundError when running test created using the transport archetype |
MULE-5775 |
Modules: CXF |
cxf proxy does not return fault to the actual caller |
EE-2604 |
Transport: JMS |
JMS to JMS synchronous bridge loses some messages (< 0.01% are lost) |
EE-2603 |
Core: Cluster |
Cluster node balancing creates single point of failure for approximately 25 minutes, than corrects itself |
EE-2583 |
Transport: WebsphereMQ |
Reply-To doesn’t work for WMQ transport |
EE-2539 |
Core: (other) |
ReplyTo property is lost because is not properly propagated between events |
EE-2523 |
"Modules: JBoss Transactions, Transport: JDBC" |
Database connection pooling with XA transaction |
EE-2503 |
Core: API |
<response> block is executed after ReplyTo message is sent |
EE-2502 |
Core: (other) |
Until Successful router should be supported in a cluster |
EE-2479 |
Core: (other) |
Issue running test after using transport archetype |
EE-2442 |
Core: API |
Provide transaction lifecycle information |
EE-2438 |
Core: (other) |
Performance of Mule ESB decreases after deploying agent to the system. |
EE-2429 |
Core: Exception Handling |
Business Event flow message status is shown as complete even when all the messages inside of it have failed. |
EE-2204 |
"Modules: High Availability, Transport: WebsphereMQ" |
WMQ + HA + Widget Example dropping messages |
MMC-1096 |
Flows & Services |
Flow Analyzer not showing nor auditing all the selected applications and flows |
MMC-1086 |
Business Event Analyzer |
Wrong Event appears to be generated in Business Event Analyzer |
MMC-1082 |
Business Event Analyzer |
"On Business Events, transaction details, not all events processed are persisted." |
MMC-1054 |
Alerts |
Alerts are not triggered on Mule 3.1.3. |
MMC-1039 |
Administration |
Verify LDAP support in MMC |
MMC-1012 |
Business Event Analyzer |
"On Administration, Admin Shell, cleanup script does not work when persistent events are in the millions." |
MMC-882 |
Generic (other) UI |
Missing localization in MMC |
Fixed in This Release
Mule version 3.2.1 builds on the features added in version 3.2.0 and fixes the following issues.
| Key | Component/s | Summary |
|---|---|---|
MULE-5866 |
Connectors |
DevKit documentation links swapped |
MULE-5861 |
Transport: HTTP(S) / Jetty |
"On exception, HTTP transport sends a response before calling the exception strategy" |
MULE-5855 |
Transport: JMS |
JMS Selector |
MULE-5853 |
Core: Expressions |
#[map-payload:key1,key2?] does not evaluate correctly" |
MULE-5847 |
Schema |
Sub-flow doesn’t admit doc name causing errors when creating them in Mule Studio |
MULE-5844 |
Core: Components |
Mule loosing session variables after a collection spllitter / aggregator |
MULE-5843 |
Schema |
Global Processing Strategy not admitting doc attribute |
MULE-5840 |
Core: Transports |
Deadlock due to JdbcMessageReceiver.processMessage() gets database connection that’s never used |
MULE-5839 |
Core: (other) |
Cache key generation errors should be ignored |
MULE-5837 |
Core: Components |
Error at startup when a sub-flow is invoked twice via flow-ref |
MULE-5831 |
Transport: JMS |
JMSConnector.closeQuietly should catch Exception not JMSException |
MULE-5830 |
Core: (other) |
Cached events are updated after being cached |
MULE-5824 |
Transport: File |
File Connector deletes the files when streaming=true and autoDelete=true in case of an Exception |
MULE-5812 |
Build: Maven |
Compiling Mule 3.x / 3.2.x fails because jsch-0.1.44.jar is corrupted in Maven central |
MULE-5811 |
Core: Endpoints |
Jetty SSL connector does not support the webapps element |
MULE-5808 |
Core: Exception Handling |
Mule not invoking exception strategy when an exception is thrown in asynchronous flow |
MULE-5807 |
Core: (other) |
NPE in MessageEnricher if enrichment processor returns null. |
MULE-5806 |
Core: Endpoints |
<poll> should not trigger flow if nested processor returns NullPayload |
MULE-5805 |
Core: Routing / Filters |
until-successful doesn’t correctly re-hydrate MuleEvents from ObjectStore |
MULE-5802 |
Modules: Scripting |
classloader cannot load interface class in script component binding |
MULE-5795 |
Documentation / Website |
Modules Reference page links missing. |
MULE-5790 |
Core: (other) |
"During load testing, the response transformer doesn’t receive the correct messages value (in IBM JVM)" |
MULE-5786 |
Schema |
Remove polling frequency attribute for JDBC outbound endpoint |
MULE-5783 |
Core: Endpoints |
Dynamic endpoints are not working when connector-ref is used |
MULE-5777 |
Examples / Tutorials |
Bookstore example admin war file doesn’t work |
MULE-5776 |
Core: Configuration |
Jetty and Ajax transport do not extend correct schema type and are therefore missing various configuration options |
MULE-5773 |
Examples / Tutorials |
Mule ESB Examples README.txt file mentions ant for all exmaples |
MULE-5759 |
Core: (other) |
org.mule.context.notification.ListenerSubscriptionPair leaks |
MULE-5756 |
Tools: Archetypes |
Fantasy domain pointed when creating a mule module using archetype |
MULE-5744 |
Core: Routing / Filters |
NPE using a filter-ref in a when element |
MULE-5717 |
"Modules: XML, XSLT, XPath, SXC" |
"Calls to Jaxen in XPathExpressionEvaluator are not synchronized, cause race conditions." |
MULE-5671 |
Core: Configuration |
Configuration.getPolicy blocked! |
MULE-5631 |
Transport: HTTP(S) / Jetty |
Mule goes into an infinite loop if you specify a keystore that doesn’t exist |
MULE-5628 |
Modules: Jersey |
Mule breaks multipart/form-data encoded messages |
MULE-5612 |
Transport: HTTP(S) / Jetty |
NPE on initialise when using jetty-ssl with CXF jaxws-service |
MULE-5544 |
Core: API |
Component cannot be used inside of an enricher |
MULE-5386 |
"Transport: AJAX, Transport: HTTP(S) / Jetty" |
Enable property placeholders in static content served over http |
MULE-5365 |
Core: Routing / Filters |
Allow using a sub-flow in message-filter/@onUnaccepted |
MULE-5123 |
Modules: CXF |
CXF databinding element doesn’t work |
MULE-4599 |
Core: API |
dispose() method not called on transformer that implements Disposable |
EE-2571 |
Examples / Tutorials |
Notification Example does not show heartbeat nor created notifications |
EE-2570 |
Modules: High Availability |
Clustering rebalancing is unstable |
EE-2561 |
Transport: CXF |
CXF - NullPointerException in LazyDataSource |
EE-2553 |
Core: Configuration |
Need the ability to force command line system properties to take precedence over props files for iON (now known as CloudHub) deployment |
EE-2550 |
Core: Transports |
Root message ID is not propagated when a message is sent Mule→Mule |
EE-2545 |
Core: Lifecycle |
Error at startup when a sub-flow is invoked twice via flow-ref |
EE-2544 |
Core: Registry |
Explicit queue profiles can cause unclustrered default object stores to be used |
EE-2537 |
Transport: HTTP/ HTTPS |
http-security-filter doesn’t cause browser to ask for credentials |
EE-2529 |
Transport: HTTP/ HTTPS |
Http endpont are created every time the url used to invoke them changes. |
EE-2526 |
Transport: (other) |
XA transactions don’t work with ActiveMQ |
EE-2524 |
Modules: (other) |
classloader cannot load interface class in script component binding |
EE-2516 |
Transport: JMS |
JMSConnector.closeQuietly should catch Exception not JMSException |
EE-2513 |
"Core: Configuration, Transport: JDBC" |
CE applications that create JDBC or FTP connectors will not run in EE (including iON, which is now known as CloudHub) |
EE-2512 |
Transport: JMS |
Connection leak with transactional JMS |
EE-2510 |
Core: Components |
Mule loosing session variables after a collection spllitter / aggregator |
EE-2509 |
Transport: File |
File Connector deletes the files when streaming=true and autoDelete=true in case of an Exception |
EE-2500 |
Core: Components |
Caching (cache:cache-processor) |
EE-2496 |
Build: Maven |
populate_m2_repo fails on windows 7 |
EE-2485 |
Examples / Tutorials |
Widget example not working on a distributed environment |
EE-2481 |
Build: Maven |
populate_m2_repo throws ClassNotFoundException |
EE-2477 |
Examples / Tutorials |
Widget example fails to compile - problem with dependencies |
EE-2473 |
Core: (other) |
"During load testing, the response transformer doesn’t receives the correct messages value (in IBM JVM)" |
EE-2469 |
Transport: WebsphereMQ |
ObjectToWMQJmsMessage does not fix invalid jms mesage property keys |
EE-2461 |
Core: (other) |
"On Business Events tab, two flow messages are being shown sometimes for one invocation. One of them has no events inside." |
EE-2460 |
Core: (other) |
"On Business Events tab, All and Split component event results are always ""failed""" |
EE-2456 |
Transport: WebsphereMQ |
<wmq:message-to-object-transformer/> throws IllegalStateException when used in WMQ inbound-endpoints |
EE-2454 |
Transport: WebsphereMQ |
Empty response block in WMQ endpoints throws NPE at mule startup |
EE-2443 |
Core: API |
Allow to access endpoint execution time via EndpointNotification |
EE-2439 |
"Modules: XML, XSLT, XPath" |
XSLT Transformer leaks memory |
EE-2432 |
Core: Routing / Filters |
NPE using a filter-ref in a when element |
EE-2411 |
Core: API |
Event Analyzer reports a single transaction as two transactions |
EE-2407 |
"Core: Lifecycle, Core: Transports, Transport: WebsphereMQ" |
WMQ jars found but not loaded/used during application initialization |
EE-2377 |
"Modules: XML, XSLT, XPath" |
"Calls to Jaxen in XPathExpressionEvaluator are not synchronized, cause race conditions." |
EE-2351 |
Documentation / Website |
Mule.xsd contains incorrect information on filters |
EE-2340 |
Core: Exception Handling |
Transaction contexts are not propagated to exception strategies |
EE-2306 |
Core: (other) |
MULE-5601 Implement caching message processor |
MMC-1108 |
Administration: Alerts |
Cannot create node up/down alerts for nodes in a cluster as required for MMC 3.2 |
MMC-1105 |
Clustering |
Deleting a group with cluster in it is provoking 'Error communicating with server' |
MMC-1091 |
Administration: Alerts |
Clusters should not be listed in alert definitions (not supported in 3.2.0 or 3.2.1) |
MMC-1079 |
"Alerts, Generic (other) UI" |
"Alerts - GUI, there are three question marks ??? displayed after the ""Server or Group???"" element. Is this really required, looks like a UI mistake." |
MMC-1078 |
"Clustering, Dashboards" |
"Clustering, Server Metrics chart ""Flow Throughput"" does not work for clustered instances, no metrics being gathered." |
MMC-1065 |
Deployments |
Unable to select version in Deployment Scenario screen |
MMC-1062 |
Business Event Analyzer |
"On Business Events, event details, TransactionMessageProcessor is shown when it should not be." |
MMC-1056 |
Build/Distributions |
"On mule-config.xml, core and jetty schemas point at 3.1 instead of 3.2." |
MMC-1053 |
Common Services |
"MMC creates ""tracking"" directory in the current directory where is launched from" |
MMC-1051 |
Agent |
MMC Agent can be successfully deployed in Mule CE |
MMC-1044 |
Generic (other) UI |
Verify MMC 3.2 is backward compatible with MMC 3.1.x |
MMC-1043 |
Administration |
Typo in Add User pane in the Administration tab |
MMC-1037 |
Business Event Analyzer |
"On Business Events tab, opened flow message details are not refresh when clicking on refreshed instance in Summary tab" |
MMC-1036 |
Business Event Analyzer |
Business Event Analyzer - custom event metadata requires a popup window to view; make it easier to view metadata |
MMC-1034 |
Documentation |
All deprecated Rest API documentation pages should be removed from production. |
MMC-1033 |
Business Event Analyzer |
"On Business Events, queries by event details fail after some minutes with frozen UI meanwhile." |
MMC-1028 |
Flows & Services |
"On Flows tab, Business friendly names are not being shown." |
MMC-1022 |
Business Event Analyzer |
"On Event Analyzer, Processing Time, using m as time unit is allowed, but system does not process it." |
MMC-1016 |
Servers |
"On Servers tab, if cluster item is clicked in the left side tree panel, the cluster view is not opened." |
MMC-1014 |
Servers |
MMC List Servers shows negative stopped and paused services |
MMC-1010 |
"Alerts, Clustering, Servers" |
Alert Keeps Track of Server after adding it to a cluster |
MMC-1008 |
Business Event Analyzer |
"On Business Events tab, Salesforce exception being shown doesn’t say the reason why it failed. Mule log does." |
MMC-1003 |
Business Event Analyzer |
"On Business Events tab, flow messages sorting is not respected after clicking search button" |
MMC-995 |
Business Event Analyzer |
"On Business Events tab, endpoints do not have result neither processing time" |
MMC-989 |
Clustering |
"On Servers, create cluster, when node name is longer than available window width, the name is truncated instead of appearing an horizontal scroll bar." |
MMC-985 |
Business Event Analyzer |
"On Event Analyzer, when database connection is broken, no error message is displayed on the UI." |
MMC-976 |
Generic (other) UI |
No user-friendly error message when selecting offline server in Flows tab |
MMC-966 |
Business Event Analyzer |
"On Event Analyzer → Search, ""event: Type"" criteria should only offer ""Custom"", and ""Default"" values." |
MMC-960 |
Business Event Analyzer |
"On Event Analyzer, when no transactions are found after a query, that information should be displayed in a format similar as the used to display results instead of a pop up." |
MMC-948 |
Generic (other) UI |
Edit server info: if name contains a slash there is an error but no reason given for the error |