What's New in Mule Enterprise Version 2.1
Mule Enterprise Version 2.1 includes Mule Enterprise Edition 2.1.3 and Mule HQ 3.5.0. This page describes the major new and changed functionality, the issues that have been fixed, and known issues in this release.
Mule 2.1 is an older release. For information on what's new in the latest release of Mule, see What's New in This Release.
New Features
This section describes the new features exclusive to Mule Enterprise Version 2.1. Note that this release also includes all the new features in Mule Community Edition Versions 2.0 through 2.1.2, such as the powerful new configuration based on XML schemas. For more information, see What's New in Mule 2.0.
Migration Tool
The principal new feature of Mule Community Edition 2.0 was a powerful new schema-based configuration style leveraging Spring's Extensible XML Authoring. This approach makes configuration much simpler. In Mule 2.1 Enterprise Edition, you can use a migration tool to help convert your existing Mule 1.x configuration files to the Mule 2.1 format. For complete information, see the Migration Tool on the Mule Customer Portal.
For more information on the new configuration format, see [XML Configuration]. For more information on what changed from Mule 1.x to Mule 2.x, see Migrating Mule 1.x to 2.0, Migrating Mule 2.0 to 2.1, and Migrating Mule 2.1 to 2.1.2.
Retry Policies
Retry policies configure how a connector behaves when its connection fails. Retry policies were implemented in Mule 2.1 CE to replace reconnection strategies. Mule 2.1 EE includes several standard retry policies available that you can configure using the Retry schema.
For more information, see [Configuring Retry Policies].
Official Support for the RESTpack
The Mule RESTpack is now officially supported as part of Mule Enterprise 2.1. For more information, see [Using the Mule RESTpack].
Improvements to Mule HQ
Mule Enterprise Version 2.1 includes Mule HQ 3.5.0, which provides improvements to Mule HQ including bug fixes (see Fixed Issues below) and performance enhancements.
Improvements to JDBC Transport
The Premium JDBC transport includes much faster performance and now provides batch and cursor support. For more information, see JDBC Transport.
CXF Transport Support for XML Input
Previously, the CXF transport took JAXB POJOs as the web service payload, requiring transformation to JAXB. Now, the CXF transport can handle XML payloads without transformation. For more information, see CXF Transport.
Extended QA Certification
The MuleSource Quality Assurance team has extended its certification of Mule, ensuring that the product is of greater quality than ever before. For a list of certified platforms, see Supported Platforms.
Changed Functionality
This section describes the functionality in this release that has changed from a previous version.
Mule Configuration File Changes
Mule configuration files are now based on XML schemas rather than a DTD. For complete information, see Whats New in Mule 2.0.
Known Issues
This section describes the major known issues in this release and how to work around each issue.
- In Mule EE 2.1.3, if you want to run the Webapp example using Maven, you must first modify its POM file and add the following dependency:
<dependency>
<groupId>org.mule.transports</groupId>
<artifactId>mule-transport-cxf</artifactId>
<version>${muleVersion}</version>
<exclusions>
<exclusion>
<groupId>org.apache.ws.security</groupId>
<artifactId>wss4j.osgi</artifactId>
</exclusion>
</exclusions>
</dependency>
- If you are experiencing agent-server communication problems with Mule HQ, upgrade to JRE 1.5 or 1.6 by setting the environment variable HQ_JAVA_HOME for MuleHQ agent and server.
- In Mule HQ, if a configuration file cannot be found or the wrong user ID or password are used to access JMX, the error message simply says "Mule Enterprise Edition is already running."
Fixed Issues
Mule Enterprise Version 2.1 includes many new features and fixes developed on Mule Community Edition as well as Mule Enterprise Edition. For a list of the Community fixes, see Mule Community Version 2.1.2.
Following is a list of issues fixed specifically for Mule Enterprise Version 2.1 including Mule HQ. Click a column heading to sort by that column.
| Issue Type | Key | Component/s | Summary | Version Fixed |
| New Feature | EE-243 | Build: (other) | 1.4->2.0 Migration Design Tool Phase 1 | 2.1.0 |
| Task | EE-770 | Build: (other) | Update assembly white-lists and exclude libs in pom's where needed | 2.1.0 |
| Bug | EE-795 | Build: (other) | populate_m2_repo throws ClassNotFoundException | 2.1.0 |
| Bug | EE-811 | Build: (other) | SwitchLicenseHeaders.groovy in EE doesn't work on Win platforms | 2.1.0 |
| Task | EE-846 | Build: Maven | Synchronize (upgrade) Mule EE pom versions | 2.1.0 |
| Improvement | EE-606 | Core: (other) | Need to support the graceful shutdown feature. | 2.1.0 |
| Bug | EE-7 | Core: (other) | Rework recursive ConnectionStrategy behaviour | 2.1.0 |
| Bug | EE-884 | Core: (other) | populate_m2_repo throws NoClassDefFoundError: org/apache/commons/cli/ParseException | 2.1.0 |
| Bug | EE-729 | Core: Configuration | "Synchronous" attribute set on an inbound endpoint carries over into endpoints in catch-all strategy | 2.1.0 |
| Task | EE-734 | Core: Configuration | Implement Retry Policies (ex-Reconnection Strategies) for 2.x | 2.1.0 |
| New Feature | EE-254 | Core: Transports | JDBC Connector: More Support for Stored Procedures, including CURSOR support | 2.1.0 |
| Improvement | EE-762 | Core: Transports Transport: HTTP/ HTTPS Transport: TCP / UDP / SSL / Multicast | DynamicURIOutboundEndpoint as key of dispatcherSocketsPool in UdpConnector causes port leaking | 2.1.0 |
| New Feature | EE-328 | Modules: XML, XSLT, XPath | Support XSLT and XPath 2.0 | 2.1.0 |
| Improvement | EE-213 | Modules: XML, XSLT, XPath Transport: SOAP / WSDL Transport: XFire | Improvement on SOAP and XML Processing Components | 2.1.0 |
| Bug | EE-582 | Transport: CXF | CXF on port 443 via SSL throws EndpointNotFoundException | 2.1.0 |
| Improvement | EE-601 | Transport: CXF | 1.6.1 EE CXF only takes Jaxb POJO as the web service payload. CXF needs to support web service client invocation input format in xml | 2.1.0 |
| Bug | EE-753 | Transport: CXF | Serving out WSDL over the VM protocol with CXF does not work | 2.1.0 |
| Task | EE-592 | Transport: FTP | Port Premium FTP transport to 2.0 | 2.1.0 |
| Improvement | EE-720 | Transport: HTTP/ HTTPS | Http Request header properties are stripped off when dispatching by HttpClientMessageDispatcher | 2.1.0 |
| Task | EE-464 | Transport: JDBC | Complete porting of premium JDBC transport to Mule 2.0 | 2.1.0 |
| Improvement | EE-600 | Transport: JDBC | Support JDBC batch stored procedure call | 2.1.0 |
| Bug | EE-603 | Transport: JMS | A message containing a list of arbitrary objects cannot be posted to JBoss Messaging | 2.1.0 |
| Bug | EE-818 | Transport: mqseries | MQSeriesMessageDispatcher should get transformed payload instead of original payload | 2.1.0 |
| Bug | EE-821 | Transport: mqseries | WMQ transport does not implement MessageRequester interface | 2.1.0 |
| Bug | EE-821 | Transport: mqseries | WMQ transport does not implement MessageRequester interface | 2.1.0 |
| Bug | EE-755 | Transport: SOAP / WSDL | WSProxyService doesn't invoke transformers | 2.1.0 |
| Bug | EE-554 | Build: JDK Compatibility | Certify RHEL 5.2 x64 w/ 64bit JDK | 2.1.1 |
| Bug | EE-937 | Build: Libraries, Examples/Tutorials | populate_m2_repo does not download muleesb pom | 2.1.1 |
| Bug | EE-896 | Examples / Tutorials | populate_m2_repo failure | 2.1.1 |
| Bug | EE-220 | Transport: (Other) | Add official support for REST pack | 2.1.1 |
| Improvement | EE-733 | Transport: HTTP/ HTTPS | HttpMessageAdapter should create a payload of type HttpRequest (which includes all passed parameters) | 2.1.1 |
| New Feature | EE-764 | Transport: HTTP/ HTTPS | Populate "Connection" and "Keep-Alive" HTTP headers based on "keepAlive" and "keepAliveTimeOut" settings in HTTP connector | 2.1.1 |
| Bug | EE-1017 | Transport: JDBC | JdbcLargeDatasetFunctionalTestCase is failing | 2.1.1 |
| Bug | EE-713 | Transport: JMS | JMS connection recovery should also recycle the JNDI connection when needed | 2.1.1 |
| Task | EE-797 | Transport: JMS | Verify fix for EE-782 in 2.1 EE (Reconnection strategy broken in 1.6.2) | 2.1.1 |
| Task | EE-775 | Transport: mqseries | Migrate the WebsphereMQ connector to 2.0 | 2.1.1 |
| Bug | EE-921 | Build: Libraries / Dependencies Examples / Tutorials | Error when trying to run JDBC example | 2.1.2 |
| Task | EE-1037 | Core: (other) | Workaround to configure asynchronous retry in 2.1.x | 2.1.2 |
| Bug | EE-1044 | Core: (other) | Asynchronous retry policy never seems to connect properly | 2.1.2 |
| Bug | EE-932 | Core: (other) Transport: JMS | Retry policy is broken in 2.1.1 | 2.1.2 |
| Bug | EE-117 | Modules: (other) | Classpath Issue with "populate_m2_repo" | 2.1.2 |
| Bug | EE-1029 | Transport: CXF | CXF connector doesn't work with Jetty connector in Mule 2.1 | 2.1.2 |
| Sub-task | EE-802 | Transport: CXF | Verify fix for EE-716 in 2.1 EE (CXF does not seem to fully support servlets) | 2.1.2 |
| Bug | EE-1347 | Core: Components | WSProxyService doesn't serve local WSDL (regression bug) | 2.1.3 |
| Bug | EE-1293 | Core: Lifecycle | GenericLifecycleManager uses hash set for completedPhases list, which incorrectly assumes a consistent ordering of elements | 2.1.3 |
| Bug | EE-1350 | Examples / Tutorials | LoanBroker doesn't build when completely offline after running populate_m2_repo | 2.1.3 |
| Bug | EE-1349 | Examples / Tutorials | Building examples with Maven fails for missing core test artifacts | 2.1.3 |
| Bug | EE-1269 | Modules: Management / JMX | Average Response Time not calculated based on interval selected, inconsistent with other service measurements | 2.1.3 |
| Bug | EE-1106 | Transport: (other) | AbstractReceiverServlet ignores WWW-Authenticate property | 2.1.3 |
| Bug | EE-1128 | Transport: CXF | CXF doesn't support jetty-ssl protocol | 2.1.3 |
| Improvement | EE-1233 | Transport: CXF | Unable to "serve up" WSDL when using proxy='true' with CXF inbound endpoint | 2.1.3 |
| Bug | EE-1334 | Transport: CXF | One way operations with CXF proxies fail | 2.1.3 |
| Bug | EE-1339 | Transport: CXF | CXF Proxy over JMS doesn't work | 2.1.3 |
| Bug | EE-1333 | Transport: JMS | JmsConnector ignores maxRedelivery setting and tries to redeliver message infinitely | 2.1.3 |
| Bug | EE-1275 | Transport: mqseries | Retry policy is broken in 2.1.2 | 2.1.3 |
| Improvement | MULEHQ-165 | Mule HQ | Disabled phonehome, but hq.updateStatusMode config option is still set to Major | 3.5.0 |
| Bug | MULEHQ-177 | Mule HQ | MuleCenter. Availability of servers, where a patch was installed, are not displayed | 3.5.0 |
| Improvement | MULEHQ-179 | Mule HQ | Modify default Mule Availability metric collection interval to 1 min | 3.5.0 |
| Improvement | MULEHQ-180 | Mule HQ | Implement ability to mass change of metrics collection intervals of all mule services | 3.5.0 |
| Task | MULEHQ-182 | Mule HQ | Determine changes in HQ Agent between r84 and RC1 (see RC2 too) | 3.5.0 |
| Sub-task | MULEHQ-184 | Mule HQ | Can't bring resource back to the auto-discovery queue after it had been skipped | 3.5.0 |
| Sub-task | MULEHQ-187 | Mule HQ | Create auto update configuration for not approved server | 3.5.0 |
| Sub-task | MULEHQ-188 | Mule HQ | User friendly return message | 3.5.0 |
| Bug | MULEHQ-197 | Mule HQ | MuleHQ agents only works with Mule versions 1.3 CE/EE and 1.4 CE/EE | 3.5.0 |
| Task | MULEHQ-209 | Mule HQ | Create/reconfigure MuleHQ build plans and have them generate Artifacts | 3.5.0 |
| Bug | MULEHQ-210 | Mule HQ | mule-sdk utility references commons-cli, but it is not there in HQ server deployment dir | 3.5.0 |
| Bug | MULEHQ-211 | Mule HQ | Can't detect Mule product version due to missing entries in Mule 2.1.x MANIFEST.MF | 3.5.0 |
| Task | MULEHQ-212 | Mule HQ | All MuleSource source files should have a proper license header | 3.5.0 |
| Task | MULEHQ-214 | Mule HQ | Migrate XPath expressions in MuleServerDetector for new XSD-based configs | 3.5.0 |
| Task | MULEHQ-215 | Mule HQ | Re-implement Mule JMX domain detection for Mule 2.x | 3.5.0 |
| Bug | MULEHQ-217 | Mule HQ | Mule no longer exposes Endpoints and Routers via JMX | 3.5.0 |
| Bug | MULEHQ-219 | Mule HQ | MuleCenter doesn't list registered Mule servers | 3.5.0 |
| Bug | MULEHQ-220 | Mule HQ | Cold Start command should pass Mule's server ID as a parameter | 3.5.0 |
| Bug | MULEHQ-222 | Mule HQ | Show Log link isn't rendered for Mule 2 servers | 3.5.0 |
| Bug | MULEHQ-223 | Mule HQ | Config file value isn't properly auto-discovered for Mule 2 | 3.5.0 |