Access Keys:
Skip to content (Access Key - 0)

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 TypeKeyComponent/sSummaryVersion Fixed
New FeatureEE-243Build: (other)1.4->2.0 Migration Design Tool Phase 12.1.0
TaskEE-770Build: (other)Update assembly white-lists and exclude libs in pom's where needed2.1.0
BugEE-795Build: (other)populate_m2_repo throws ClassNotFoundException2.1.0
BugEE-811Build: (other)SwitchLicenseHeaders.groovy in EE doesn't work on Win platforms2.1.0
TaskEE-846Build: MavenSynchronize (upgrade) Mule EE pom versions2.1.0
ImprovementEE-606Core: (other)Need to support the graceful shutdown feature.2.1.0
BugEE-7Core: (other)Rework recursive ConnectionStrategy behaviour2.1.0
BugEE-884Core: (other)populate_m2_repo throws NoClassDefFoundError: org/apache/commons/cli/ParseException2.1.0
BugEE-729Core: Configuration"Synchronous" attribute set on an inbound endpoint carries over into endpoints in catch-all strategy2.1.0
TaskEE-734Core: ConfigurationImplement Retry Policies (ex-Reconnection Strategies) for 2.x2.1.0
New FeatureEE-254Core: TransportsJDBC Connector: More Support for Stored Procedures, including CURSOR support2.1.0
ImprovementEE-762Core: Transports
Transport: HTTP/ HTTPS
Transport: TCP / UDP / SSL / Multicast
DynamicURIOutboundEndpoint as key of dispatcherSocketsPool in UdpConnector causes port leaking2.1.0
New FeatureEE-328Modules: XML, XSLT, XPathSupport XSLT and XPath 2.02.1.0
ImprovementEE-213Modules: XML, XSLT, XPath
Transport: SOAP / WSDL
Transport: XFire
Improvement on SOAP and XML Processing Components2.1.0
BugEE-582Transport: CXFCXF on port 443 via SSL throws EndpointNotFoundException2.1.0
ImprovementEE-601Transport: CXF1.6.1 EE CXF only takes Jaxb POJO as the web service payload. CXF needs to support web service client invocation input format in xml2.1.0
BugEE-753Transport: CXFServing out WSDL over the VM protocol with CXF does not work2.1.0
TaskEE-592Transport: FTPPort Premium FTP transport to 2.02.1.0
ImprovementEE-720Transport: HTTP/ HTTPSHttp Request header properties are stripped off when dispatching by HttpClientMessageDispatcher2.1.0
TaskEE-464Transport: JDBCComplete porting of premium JDBC transport to Mule 2.02.1.0
ImprovementEE-600Transport: JDBCSupport JDBC batch stored procedure call2.1.0
BugEE-603Transport: JMSA message containing a list of arbitrary objects cannot be posted to JBoss Messaging2.1.0
BugEE-818Transport: mqseriesMQSeriesMessageDispatcher should get transformed payload instead of original payload2.1.0
BugEE-821Transport: mqseriesWMQ transport does not implement MessageRequester interface2.1.0
BugEE-821Transport: mqseriesWMQ transport does not implement MessageRequester interface2.1.0
BugEE-755Transport: SOAP / WSDLWSProxyService doesn't invoke transformers2.1.0
BugEE-554Build: JDK CompatibilityCertify RHEL 5.2 x64 w/ 64bit JDK2.1.1
BugEE-937Build: Libraries, Examples/Tutorialspopulate_m2_repo does not download muleesb pom2.1.1
BugEE-896Examples / Tutorialspopulate_m2_repo failure2.1.1
BugEE-220Transport: (Other)Add official support for REST pack2.1.1
ImprovementEE-733Transport: HTTP/ HTTPSHttpMessageAdapter should create a payload of type HttpRequest (which includes all passed parameters)2.1.1
New FeatureEE-764Transport: HTTP/ HTTPSPopulate "Connection" and "Keep-Alive" HTTP headers based on "keepAlive" and "keepAliveTimeOut" settings in HTTP connector2.1.1
BugEE-1017Transport: JDBCJdbcLargeDatasetFunctionalTestCase is failing2.1.1
BugEE-713Transport: JMSJMS connection recovery should also recycle the JNDI connection when needed2.1.1
TaskEE-797Transport: JMSVerify fix for EE-782 in 2.1 EE (Reconnection strategy broken in 1.6.2)2.1.1
TaskEE-775Transport: mqseriesMigrate the WebsphereMQ connector to 2.02.1.1
BugEE-921Build: Libraries / Dependencies Examples / TutorialsError when trying to run JDBC example2.1.2
TaskEE-1037Core: (other)Workaround to configure asynchronous retry in 2.1.x2.1.2
BugEE-1044Core: (other)Asynchronous retry policy never seems to connect properly2.1.2
BugEE-932Core: (other)
Transport: JMS
Retry policy is broken in 2.1.12.1.2
BugEE-117Modules: (other)Classpath Issue with "populate_m2_repo"2.1.2
BugEE-1029Transport: CXFCXF connector doesn't work with Jetty connector in Mule 2.12.1.2
Sub-taskEE-802Transport: CXFVerify fix for EE-716 in 2.1 EE (CXF does not seem to fully support servlets)2.1.2
BugEE-1347Core: ComponentsWSProxyService doesn't serve local WSDL (regression bug)2.1.3
BugEE-1293Core: LifecycleGenericLifecycleManager uses hash set for completedPhases list, which incorrectly assumes a consistent ordering of elements2.1.3
BugEE-1350Examples / TutorialsLoanBroker doesn't build when completely offline after running populate_m2_repo2.1.3
BugEE-1349Examples / TutorialsBuilding examples with Maven fails for missing core test artifacts2.1.3
BugEE-1269Modules: Management / JMXAverage Response Time not calculated based on interval selected, inconsistent with other service measurements2.1.3
BugEE-1106Transport: (other)AbstractReceiverServlet ignores WWW-Authenticate property2.1.3
BugEE-1128Transport: CXFCXF doesn't support jetty-ssl protocol2.1.3
ImprovementEE-1233Transport: CXFUnable to "serve up" WSDL when using proxy='true' with CXF inbound endpoint2.1.3
BugEE-1334Transport: CXFOne way operations with CXF proxies fail2.1.3
BugEE-1339Transport: CXFCXF Proxy over JMS doesn't work2.1.3
BugEE-1333Transport: JMSJmsConnector ignores maxRedelivery setting and tries to redeliver message infinitely2.1.3
BugEE-1275Transport: mqseriesRetry policy is broken in 2.1.22.1.3
ImprovementMULEHQ-165Mule HQDisabled phonehome, but hq.updateStatusMode config option is still set to Major3.5.0
BugMULEHQ-177Mule HQMuleCenter. Availability of servers, where a patch was installed, are not displayed3.5.0
ImprovementMULEHQ-179Mule HQModify default Mule Availability metric collection interval to 1 min3.5.0
ImprovementMULEHQ-180Mule HQImplement ability to mass change of metrics collection intervals of all mule services3.5.0
TaskMULEHQ-182Mule HQDetermine changes in HQ Agent between r84 and RC1 (see RC2 too)3.5.0
Sub-taskMULEHQ-184Mule HQCan't bring resource back to the auto-discovery queue after it had been skipped3.5.0
Sub-taskMULEHQ-187Mule HQCreate auto update configuration for not approved server3.5.0
Sub-taskMULEHQ-188Mule HQUser friendly return message3.5.0
BugMULEHQ-197Mule HQMuleHQ agents only works with Mule versions 1.3 CE/EE and 1.4 CE/EE3.5.0
TaskMULEHQ-209Mule HQCreate/reconfigure MuleHQ build plans and have them generate Artifacts3.5.0
BugMULEHQ-210Mule HQmule-sdk utility references commons-cli, but it is not there in HQ server deployment dir3.5.0
BugMULEHQ-211Mule HQCan't detect Mule product version due to missing entries in Mule 2.1.x MANIFEST.MF3.5.0
TaskMULEHQ-212Mule HQAll MuleSource source files should have a proper license header3.5.0
TaskMULEHQ-214Mule HQMigrate XPath expressions in MuleServerDetector for new XSD-based configs3.5.0
TaskMULEHQ-215Mule HQRe-implement Mule JMX domain detection for Mule 2.x3.5.0
BugMULEHQ-217Mule HQMule no longer exposes Endpoints and Routers via JMX3.5.0
BugMULEHQ-219Mule HQMuleCenter doesn't list registered Mule servers3.5.0
BugMULEHQ-220Mule HQCold Start command should pass Mule's server ID as a parameter3.5.0
BugMULEHQ-222Mule HQShow Log link isn't rendered for Mule 2 servers3.5.0
BugMULEHQ-223Mule HQConfig file value isn't properly auto-discovered for Mule 23.5.0
<< Previous: What's New in This Release Next: Migrating Mule 1.x to 2.0 >>
Adaptavist Theme Builder (3.3.3-conf210) Powered by Atlassian Confluence 2.10, the Enterprise Wiki.
Free theme builder license