Mule ESB 3.1.1 Release Notes
The Mule team is pleased to announce the availability of Mule ESB 3.1.1. This is a follow-up release to Mule ESB 3.1, which continues MuleSoft’s commitment to making Mule the industry’s most powerful, simplest to use, and up-to-date Open Source ESB.
| In previous versions of Mule ESB, you were required to set the MULE_HOME environment variable in order for Mule to start. As of version 3.1, the MULE_HOME variable is not required. If you have an existing MULE_HOME variable pointing to a previous version of Mule, you may see inconsistent results. Therefore, if you have previously set this variable, you should unset it. |
New in Mule ESB Version 3.1.1
Example Launcher
Both the Community and the Enterprise editions of Mule ESB Version 3.1.1 include a new Example Launcher application which allows you to discover the power of Mule right out of the box.
Documentation Improvements
A number of new reference topics are included in the Mule ESB documentation. In short, the topics listed below represent more complete, consistent, and hopefully more useful documentation for the modules and transports that constitute the core value of the Mule ESB. At the top of each new page, you can rate the usefulness of each page. Also, you can give feedback by clicking on the thumbs up or down icons at the bottom of each of these new topics.
Change to Mule Configuration Pattern Namespace
Previously, the ws-proxy pattern was in its own namespace, while others were in the core-mule namespace. As of 3.1.1, all Mule Configuration Patterns will be in this pattern namespace. The patterns' element names have been changed, though the old names are still supported for compatibility. They will be removed in a future release.
| Current element name | Previous element name |
|---|---|
pattern:bridge |
bridge |
pattern:simple-service |
simple-service |
pattern:validator |
validator |
pattern:web-service-proxy |
ws:proxy |
As part of this change, a new maven artifact mule-pattern-core has been created to contain the patterns. The artifact mule-module-ws has been deleted.
CXF upgrade
CXF has been upgraded to version 2.3.1. You can see the release notes for this CXF version at CXF 2.3.1 Release Notes.
Mule ESB Management Console
*Enterprise Edition*
-
Per-Instance ".mule" subfolders: If you are running multiple embedded MULE instances then the
.mulefolder contains a single subfolder for each instance, also preventing persistence collisions. The.mulefolder will be contained in the working directory from where the container was launched. For instance, if you start the container with something likeapache-tomcat/bin> ./run, the.mulefolder would be here:apache-tomcat-xxx/bin/.mule. -
Runtime Manager Agent port ranges: When you start a mule instance (embedded or stand-alone) that includes the MMC agent, the agent will select a port from a range to avoid collision with other agents.
The default port range is 7777-7877. This can be overridden, for example, to specify a fixed port:
./mule -M-Dmule.mmc.bind.port=7777
to specify a range:
./mule -M-Dmule.mmc.bind.port=8888-8898
Migration from Previous Versions
For instructions on migrating from a previous version, consult the Mule Migration page.
Open Issues in This Release
Open Issues
The following jiras are open against this release of Mule ESB:
| Key | Component/s | Summary | Workaround |
|---|---|---|---|
MMC-740 |
Mule Management Console |
MMC screen showing three unregistered servers at the same location |
Start multiple instances of Mule sequentially to allow proper port binding. |
EE-2113 |
Mule ESB |
The populate_m2_repo still requires MULE_HOME to be set. |
|
EE-2197 |
Mule ESB |
Widget example still requires MULE_HOME to be set. |
|
MMC-726 |
Mule Management Console |
if a mule instance is manually registered in MMC (rather than autodiscovered) then it is expected that the mule instance always be available on the same ip address and port. |
Best practice - change port range for automatic port binding to be well above the range with manual port assignment. |
MMC-765 |
Mule Management Console |
Applications/servers removed from a deployment are not undeployed from servers. Applications manually started/stopped (via MMC or by manual copy in apps/ folder) do not trigger automatic reconciliation check. Down servers are ignored during deployment operation. This might lead to inconsistencies. |
Before modifying a deployment, undeploy it, modify it, then redeploy. To remove an application from a deployment, force undeploy on the deployment before removing an app from it. When the deployment is deployed again, the removed app will not be available. |
MMC-754 |
Mule Management Console |
"After" payload is not visible in the Flow Analyzer for async blocks and one-way end-points |
N/A |
MMC-663 |
Mule Management Console |
Alert description is not displayed for raised alerts |
Although the information is not shown, it is correctly saved. To verify this, go to to alert edit mode. |
Fixed in this Release
Mule version 3.1.1 builds on the features added in version 3.1 and fixes the following issues. (All the fixes from previous 3.1 milestones are included.)
| Key | Component/s | Summary |
|---|---|---|
MULE-5426 |
Examples / Tutorials |
Mule example launcher: bookstore example missing instructions on how to set up email |
MULE-5425 |
Examples / Tutorials |
Mule example launcher: instructions to run are incorrect |
MULE-5421 |
Modules: CXF |
CXFInboundMessageProcessor does not fire message processor notification |
MULE-5420 |
Examples / Tutorials, Modules: BPM / Rules |
loanbroker-bpm message incomplete |
MULE-5417 |
Core: (other) |
Invoker MessageProcessor does not work with zero arguments |
MULE-5416 |
Core: API |
Fire MessageProcessor notifications for all message processors to enable visibility or pre/post payload for all processors |
MULE-5414 |
Examples / Tutorials, Transport: HTTP(S) / Jetty |
Jetty’s webdefault.xml can’t be read from the jar file |
MULE-5408 |
Modules: XML, XSLT, XPath, SXC |
SchemaValidationTransformer is missing |
MULE-5406 |
Modules: CXF |
WS-Addressing when used causes a NPE |
MULE-5405 |
Transport: (other) |
Serialization wire format for Remote dispatcher does not work. |
MULE-5397 |
Core: Event/Message |
Deserialization of events on another mule instance fails when endpoints don’t explictly specify a connector to use. |
MULE-5396 |
Core: Configuration |
Global components are allowed in schema but not supported |
MULE-5388 |
Core: Services |
When SimpleServices inherits a component (element) same component instance is used and this introduces lifecycle problems |
MULE-5385 |
Core: Components |
AbstractComponent rejects events with an exception if service is not fully started and messages are lost |
MULE-5384 |
Core: Services |
SedaService workManager is stopped before queue polling thread exits and messages are lost |
MULE-5376 |
Documentation / Website |
Mule 2 documentation looks like sub-elements of the Mule 3 one |
MULE-5375 |
Modules: Spring |
spring mule bean definition parsers should leave alone attributes named "xml…" |
MULE-5370 |
Core: Event/Message |
InvokeMessageProcessor replaces expressions with value of entries in maps |
MULE-5366 |
Modules: JSON |
JSON module has the incorrect schema location for the spring namespace |
MULE-5361 |
Transport: Email |
EmailMessageToString chokes on emails with no text body |
MULE-5360 |
Transport: Email |
passwords shown in the log when using email endpoints with '%40' url encoding |
MULE-5358 |
Transport: Email |
IMAP Connector throw an NPE Exception if property deleteReadMessages="false" |
MULE-5355 |
Core: Bootstrap / Standalone, Modules: CXF |
CXF interceptors get shared across applications which creates unexpected errors |
MULE-5354 |
Core: Transports |
A failed connector ends up in a state where it can not reconnect |
MULE-5350 |
Cloud Connectors |
Unable to use any http method other than GET/POST |
MULE-5347 |
Build: Distributions, Examples / Tutorials |
Mule distribution bundles empty examples/webapp |
MULE-5345 |
Examples / Tutorials |
Repackage bookstore app to use standard <jetty:webapp/> facilities |
MULE-5344 |
Build: Distributions, Examples / Tutorials |
Remove all duplicate jsps and servlet jars from the example apps |
MULE-5338 |
Core: Transports |
Custom transports fail to load when bundled in a Mule app (vs deployed in Mule system libs) |
MULE-5331 |
Core: Lifecycle |
Starting a stopped Async service results in the service NOT consuming any messages |
MULE-5325 |
Transport: HTTP(S) / Jetty |
Provide defaults and config-by-convention for <jetty:webapp/> |
MULE-5324 |
Transport: HTTP(S) / Jetty |
Bundle jsp support for <jetty:webapp/> config element |
MULE-5315 |
Transport: HTTP(S) / Jetty |
jetty:webapp should clearly display deployed apps' urls |
MULE-5290 |
Core: Transports |
Message receiver’s disconnect gets called before stop |
MULE-5267 |
Core: Routing / Filters |
Some MPs do not delegate lifecycle, mule context etc. to their the child processors |
MULE-5245 |
Examples / Tutorials |
Message are dropped when running LoanbrokerESBTestCase with load |
MULE-5244 |
Modules: CXF |
NPE in CXF when running LoanBrokerESBTestCase with load |
MULE-5189 |
Modules: CXF |
CXF and SSL (https) |
MULE-4942 |
Core: Lifecycle |
Pausing a service will still let a single message through if there was a poll on the queue happening as Pause was called |
MULE-4715 |
Modules: CXF |
MULE-4241 Re-test transport hot deployment with CXF |
EE-2188 |
Examples / Tutorials, Modules: High Availability |
Classloader issue after failover (HA) |
EE-2182 |
Modules: High Availability |
When gracefully shutting down primary node in active-passive cluster queue is emptied on shutdown |
EE-2180 |
Examples / Tutorials, Modules: High Availability |
Concurrency issue with widget (HA) example |
EE-2178 |
Core: (other), Examples / Tutorials |
Stress testing Loan Broker BPM makes Mule slow down (almost to a halt), even after the test has finished |
EE-2176 |
Core: Bootstrap / Java Service Wrapper, Modules: High Availability |
ha with mule apps incorrectly set apps to backup |
EE-2175 |
Examples / Tutorials, Modules: High Availability |
ClassCastException when running widget (HA) example |
EE-2173 |
Modules: High Availability |
The cluster transport does not handle property and attachment scopes correctly |
EE-2158 |
Transport: (other) |
Mule Remote Dispatcher does not work with Flows |
EE-2156 |
Documentation / Website |
The EE schemas need to be updated to contain a schema doc section |
EE-2143 |
Modules: (other) |
Asynchronous reconnect strategy is broken |
EE-2128 |
QA: Testing |
update SwitchVersion script to update version for automated examples testing |
EE-2080 |
Modules: High Availability |
Transactions not working with HA |
MMC-762 |
Mule Management Console |
After deleting a deployment twice, it isn’t undeployed (but the deployment IS deleted from the list) |
MMC-758 |
Mule Management Console |
Servers drop-down on Flow Analyzer screen shows invalid until a server is selected (looks bad) |
MMC-757 |
Mule Management Console |
Delete app → app undeployed, but deployment is not auto-reconciled |
MMC-755 |
Mule Management Console |
No available ports in range |
MMC-753 |
Mule Management Console |
Application is not deployed to newly registered member of a group |
MMC-751 |
Mule Management Console |
Applications are not removed when multi-group deployment is undeployed |
MMC-748 |
Mule Management Console |
On dashboard: Application portlet doesn’t show the applications for all the servers if no group is selected |
MMC-747 |
Mule Management Console |
Resolved: (MMC-747) Can’t change user permissions levels |
MMC-745 |
Mule Management Console |
No threadpool list for mule2 servers |
MMC-744 |
Mule Management Console |
Errors while creating alerts should be reported client side |
MMC-743 |
Mule Management Console |
Incomplete cleanup on alert definition update |
MMC-742 |
Mule Management Console |
Can’t add a new chart type to a server dashboard |
MMC-741 |
Mule Management Console |
Cannot name an application when adding application to repository - name field is invalid with "Mule app must be packaged as zip file." |
MMC-740 |
Mule Management Console |
Can start multiple agents at same location (ip/port) |
MMC-734 |
Mule Management Console |
Some explanation text uses Tcat terminology |
MMC-732 |
Mule Management Console |
Relocating a server may cause 'server aliasing' |
MMC-724 |
Mule Management Console |
Server down, but DashboardService.getServerCharts() is flooding the log with errors |
MMC-722 |
Mule Management Console |
Copyright notice on login page is outdated. |
MMC-712 |
Mule Management Console |
Audit: List of Message Processors is not scrollable |
MMC-711 |
Mule Management Console |
After stopping and restarting MMC, the console is reported as down when actually it is not. |
MMC-710 |
Mule Management Console |
Inbound/outbound endpoint events count |
MMC-706 |
Mule Management Console |
Deployments listing order changes after clicking on Applications tab. |
MMC-704 |
Mule Management Console |
On Applications → All Deployments, deleting an active deployment actually undeploys its associated apps instead of undeploy them and delete the deployment. |
MMC-701 |
Mule Management Console |
On Applications, Deployments continue to display Reconciled state in "Yes", even after Server is unregistered. |
MMC-699 |
Mule Management Console |
On Applications → All Deployments, deployment item on result table is not clickable anymore after coming from edit mode because of a click on Applications tab. |
MMC-697 |
Mule Management Console |
On Dashboard → Deployment Status, after adding one or more groups when configuring the portlet, no deployment info is displayed. |
MMC-696 |
Mule Management Console |
On Dashboard → Server Health, Server Down checkbox state is never saved. |
MMC-695 |
Mule Management Console |
On Servers, the treeitem "All" should indicate the number of actual registered servers. |
MMC-694 |
Mule Management Console |
When trying to register an already registered server, system does not display already paired message, but a general RPCException. |
MMC-693 |
Mule Management Console |
Privilege column heading is misspelled in Servers→Applications screen |
MMC-691 |
Mule Management Console |
Restarting the flow doesn’t work |
MMC-689 |
Mule Management Console |
On Dashboard → Server Metrics, params are not validated. |
MMC-688 |
Mule Management Console |
On Dashboard → Server Metrics, OS Memory Usage and OS Swap Usage can be added without specifying a server. |
MMC-687 |
Mule Management Console |
Admin Shell: can click "Delete" script button though no script is selected; nothing is deleted after confirming |
MMC-686 |
Mule Management Console |
On Dashboard → Server Metric, flows are no shown if a server group is selected. |
MMC-679 |
Mule Management Console |
Update copyright to 2011 in the footer |
MMC-678 |
Mule Management Console |
Unable to register agent for Mule 2.2.7 |
MMC-674 |
Mule Management Console |
Can delete the Admistrators user group; JCR Exceptions occur after deleting it |
MMC-671 |
Mule Management Console |
Invalid error highlight on Audit → Server selection |
MMC-669 |
Mule Management Console |
When defining an alert notification, error message is incorrect or not clear enough. |
MMC-667 |
Mule Management Console |
Master checkbox on Administration → User Groups is not working. |
MMC-666 |
Mule Management Console |
Email alert notification allows invalid data on To and From fields. |
MMC-665 |
Mule Management Console |
Filter not saved when creating a notification alert. |
MMC-662 |
Mule Management Console |
When creating a User Group, Description field not saved. |
MMC-652 |
Mule Management Console |
Bookstore Example does not shut down properly |
MMC-651 |
Mule Management Console |
Deployment to no group or server successful, when selected alongside a valid deployment. |
MMC-649 |
Mule Management Console |
Same app can be added multiple times to same deployment. |
MMC-648 |
Mule Management Console |
Race condition when registering Mule servers manually |
MMC-646 |
Mule Management Console |
When deploying an application, no indicator that operation is in progress is displayed. |
MMC-645 |
Mule Management Console |
Deployment status image missing while deploying. |
MMC-644 |
Mule Management Console |
When specifiying invalid name format when importing an app into the repository, operation is not completed but there is no error message |
MMC-640 |
Mule Management Console |
On Servers → <Choose server> → Server details → Dashboard → Server Metrics: No way to differentiate two charts with the same name and different constrains. |
MMC-639 |
Mule Management Console |
Incorrect data displayed on About Us dialog.. |
MMC-634 |
Mule Management Console |
MMC should prevent deployment to embedded Mule instances |
MMC-629 |
Mule Management Console |
Unable to deploy, undeploy or redeploy app using the buttons on Applications → All Deployements after restarting a server belonging to the deployment. |
MMC-627 |
Mule Management Console |
Need to change "Webapps" cloumn name to "Applications" for Deployment Status portlet |
MMC-626 |
Mule Management Console |
processing time graph is inconsistent. It drops the displayed spike. |
MMC-625 |
Mule Management Console |
first time start: all event graphs are displaying 1 req processed. Which is not true |
MMC-624 |
Mule Management Console |
Application deployed to Server Groups are not listed in the Server Deployment Status Dashboard |
MMC-621 |
Mule Management Console |
Unable to create a Chart for Services or Flows |
MMC-619 |
Mule Management Console |
Deploying the same app twice is not handled gracefully |
MMC-618 |
Mule Management Console |
Webapp that is not Mule app can be added to a deployment and deployed to empty server group successfully. |
MMC-612 |
Mule Management Console |
Deploying a second application failed (and other application that was deployed is not working) |
MMC-610 |
Mule Management Console |
MMC console doesn’t terminate properly on reload |
MMC-603 |
Mule Management Console |
Introduce Unreconciled deployment status as a first-class status |
MMC-602 |
Mule Management Console |
Files → First refresh duplicates the file list |
MMC-601 |
Mule Management Console |
Able to deploy an application to an empty server group |
MMC-589 |
Mule Management Console |
deployment fails is your deployment targets a server and a group that it’s in |
MMC-588 |
Mule Management Console |
deploying the same app in different deployments leaves the user with neither app deployed |
MMC-587 |
Mule Management Console |
Delete app from 'deployed' Deployment → app undeployed ok from Mule, but Deployment is listed as 'deployed' still |
MMC-577 |
Mule Management Console |
Audit UI should be reset when audited application/flow is no longer present |
MMC-470 |
Mule Management Console |
Agent port range support |