Mule ESB 3.3.3 Release Notes
May 15, 2013
MuleSoft is pleased to announce the release of Mule ESB 3.3.3 which offers improvements to the core Mule ESB product and the graphical IDE, Mule Studio.
These release notes apply to Mule ESB Enterprise. We have applied all of the core changes in 3.3.3 to the Enterprise runtime.
Access the MuleSoft Enterprise Customer Portal to download Mule ESB 3.3.3 Enterprise Edition and take advantage of an improved and hardened Mule ESB.
Current Release Version
Enterprise Edition | Community Edition | |
---|---|---|
ESB |
Version 3.3.3 Build e6e2269e |
n/a |
Studio |
Version 3.4.0 |
|
Management Console |
Build Number: 5731754fe4 |
n/a |
SAP Enterprise |
2.0 |
|
CMIS Connector |
1.8 |
|
Magento Connector |
1.8 |
|
MongoDB Connector |
3.0 |
|
Salesforce Connector |
5.2.0 |
|
Twilio Connector |
1.4 |
|
Twitter Connector |
2.7.3 |
Noteworthy
-
Performance improvement in Studio’s XML Validator - The performance of Studios XML Validator has been significantly improved, facilitating quicker navigation between the Visual and XML editors and reliable data persistance between editors.
-
Maven integration improvements in Studio - A new populate repository improves the experience of Maven integration and reliability in Studio.
-
Studio Anypoint Connector validation with runtime - When you run an application that contains versions of Anypoint Connectors which conflict with the version of your projects runtime, Mule displays a warning to advise you of the conflict specifics and asks if you wish to proceed to run the application.
-
Support for multiple runtimes in Studio - Beyond the Community runtime, you can download multiple Enterprise runtimes in Studio, using different runtimes with your Studio projects as desired. Read more about installing extra runtimes in Studio.
-
Upgraded CXF - The CXF framework, which Mule uses to work with Web services, is upgraded to version 2.5.9.
-
Improved cluster performance - When using a cluster, systems which involve high CPU consumption function smoothly.
-
Fixed continuations support on the Jetty transport
Hardware and Software System Requirements
For most use cases, Mule ESB 3.3.3 does not change the hardware and software system requirements established by Mule ESB 3.3.2.
Please 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 ESB 3.3.3. Please read this list before reporting any issues you may have spotted.
Mule ESB
Issue | Description |
---|---|
MULE-6833 |
GZip transformer failing |
MULE-6800 |
Thread leak on Mule redeployments for embedded |
MULE-6712 |
Old dated message processing expressions |
EE-3094 |
CXF Proxy service not honoring xsd schema location when validation is enabled |
EE-3074 |
Undeploy of the foreach example not working on windows xp/ windows server 2003 |
EE-3052 |
MEL is inconsistent with rootMessage in foreach |
EE-3046 |
HTTP Date header is should be formatted in 24-hour range |
MULE-6215 |
Inconsistent and wrong script bindings |
EE-3140 |
JDBC-EE BatchManager does not commit batch |
EE-3139 |
Special characters in SFTP outbound endpoint 'path' not allowed |
EE-3037 |
Leftover debug message left in JMS Message Dispatcher |
EE-3023 |
static-resource-handler doesn’t work when http inbound doesn’t have path attribute. |
EE-2994 |
populate_m2_repo is retrieving unnecessary jars and missing necessary jars |
Mule Studio
STUDIO-3239 |
sObject in Salesforce connector is lost in Linux |
n/a |
When installing a new ESB runtime, Studio might change the runtime version on your current projects in the workspace. This has been fix for project created with the current release but it will affect any project created with a previous version of Studio ( current: 3.4.0-201305141336 ) in your workspace. |
Mule Management Console
n/a |
Known issue: If you place a cluster in a server group, you may experience issues with deployments which target the group instead of the cluster directly. Workaround: Use the cluster as one of the direct targets of your deployments. If you experience issues, check the apps directory in your Mule(s) to to confirm that they are functional. |
n/a |
Known issue: 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. |
Fixed in this Release
Mule ESB
Issue | Description |
---|---|
EE-2755 |
MESSAGE-PROCESSOR notification events are not detected by the notification publisher |
EE-2871 |
Mule cluster graceful shutdown loses messages |
EE-2872 |
JBossTS properties getting ignored |
EE-2873 |
Missing MANIFEST.MF information do not allow to start mule while using mule-ee-distribution-embedded-3.3.x.jar |
EE-2898 |
High CPU Usage in Mule 3.3.1 Clustering |
EE-2922 |
Installing security example fails |
EE-2924 |
mule-ee-parent-poms should include the datamapper parent too |
EE-2966 |
File Transport, moveToDirectory & moveToPattern doesn’t create the output directory if streaming is true |
EE-2975 |
Provide a Locking mechanism for synchronization of Mule components in a clustered environment |
EE-2982 |
The Redelivery Policy of the RollbackExceptionStrategy doesn’t work on Cluster |
EE-2995 |
NullPointException when using splitter/aggregator in a clustered environment |
EE-3112 |
Hazelcast refuses to start with truststore (ServiceRegistry issue) |
MULE-5301 |
The MailMessageFactory adds inbound email headers to the outbound scope of the message |
MULE-5954 |
Mule cannot configure JBOSS TM properties - defaultTimeout & txReaperTimeout |
MULE-6443 |
poolingProfileType should include a variable to specify time between eviction |
MULE-6448 |
The foreach stops the flow when in a xpath collection one tag is empty |
MULE-6521 |
Mule packaging incorrectly registered by mule maven plugin |
MULE-6540 |
Provide a Locking mechanism for synchronization of Mule components |
MULE-6549 |
jBPM, MuleSendActivity.perform is not thread safe |
MULE-6550 |
Different build numbers are displayed from the same distribution |
MULE-6553 |
MESSAGE-PROCESSOR notification events are not detected by the notification publisher |
MULE-6555 |
File transport moveToPattern fails to create directories if streaming is true |
MULE-6556 |
IdempotentMessageFilter does not allow setting onUnaccepted |
MULE-6654 |
Message format is wrong in AbstractAddVariablePropertyTransformer.transformMessage() |
MULE-6809 |
When using a persisten object store keys that are not valid file names fail |
MULE-6796 |
Allow MEL expressions in cxf:property of cxf:ws-config |
MULE-6794 |
CXF WS-Security - SecurityContext is not set after successful authentication |
MULE-6791 |
Jetty inbound endpoint configured with useContinuations="true" sets http.method as outbound rather than inbound |
MULE-6790 |
File transport sets the Directory attribute incorrectly |
MULE-6788 |
Upgrade CXF to 2.5.9 |
MULE-6783 |
HTTP inbound keep-alive attribute not overriding the keepAlive attribute of HTTP connector |
MULE-6776 |
TransactedPollingMessageReceiver doesn’t call Exception Listener |
MULE-6773 |
TCP/HTTP/HTTPS Connectors: invalid maxThreadsIdle |
MULE-6768 |
After applying HTTP Basic Auth Policy, start to get a NotSerializableException |
MULE-6766 |
foreach not accepting property placeholder for batchSize |
MULE-6737 |
Application with IMAP connector doesn’t undeploy |
MULE-6732 |
HTTP(S) transport generates everlasting temporary files |
MULE-6731 |
File inbound endpoint triggers multiple flow instances if file read time is longer than pollingFrequency |
MULE-6724 |
make maven buildnumber plugin work with git |
MULE-6697 |
GZipTransformer does not support streaming |
MULE-6690 |
StringToEmailMessage doesn’t encode subject correctly |
MULE-6633 |
Typo in AsyncInterceptingMessageProcessor.isProcessAsync() |
MULE-6630 |
Expression component serializes requests |
MULE-6629 |
Concurrent modification exception when evaluation MEL expressions |
MULE-6617 |
First successful not working when used with inputstream based transports |
MULE-6616 |
mule-project-archetype:create generates a POM that uses version 1.6 of maven-mule-plugin |
MULE-6612 |
Core exports unnecessary transient dependency to junit |
MULE-6607 |
NullPointerException on commons-pool when using jdbc queries nested on inbound/outbound endpoints |
MULE-6595 |
Monitored Object Store is using the wrong class loader |
MULE-6593 |
Fligh Reservation system does not recognize JSON command on IE 9. |
MULE-6591 |
Exception on shutdown provokes app redeployment |
MULE-6590 |
Removing anchor file does not undeploy application |
MULE-6587 |
Concurrent XA transactions on same resource manager will lose messages during rollback |
MULE-6585 |
VM transport should use getSize instead of peek to determine if their are more messages |
MULE-6522 |
JDK version checking does not always work inside an IDE |
MULE-6499 |
Java version checking should not log a warning with a supported version |
MULE-6485 |
useContinuations parameter failure |
MULE-6064 |
The Default Persistent Object Store does not accept any Serializable key |
MULE-5363 |
Improper response from ws:proxy (pattern based configuration) when request header contains Accept-Encoding: gzip,deflate |
MULE-5276 |
processing.time.monitor thread leak |
EE-3075 |
CSVToMapsTransformer fails with backslash t as delimiter |
EE-3078 |
Running a SELECT query with the JTDS driver fails |
EE-3064 |
StringToEmailMessage doesn’t encode subject correct |
EE-3058 |
NullPointerException on commons-pool when using jdbc queries nested on inbound/outbound endpoints |
EE-3044 |
Exception on shutdown provokes app redeployment |
EE-3036 |
cluster & quartz, ArrayIndexOutOfBoundsException and java.lang.IllegalArgumentException: n must be positive |
EE-2932 |
First successful not working when used with inputstream based transports |
EE-2832 |
JDBC EE Batch Update, - add support to execute the query once and only once, regardles the type of payload |
EE-2827 |
web-service-proxy not copying Content-Encoding on response |
EE-2802 |
GZipTransformer does not support streaming |
MULE-6831 |
Applications deleted when deployment fails |
Mule Studio
Issue | Description |
---|---|
STUDIO-3217 |
MySQL Lookup Table not working with 3.3.3 in DataMapper |
STUDIO-3214 |
Adding a Maven dependency in a studio project doesn’t add it to an archive deployed to CloudHub |
STUDIO-3211 |
Deleting an Input argument is not automatically eliminating it from the assigned fields |
STUDIO-3204 |
Metadata from CSV with quotes on column headers has quotes in field names |
STUDIO-3198 |
Studio Takes 2 minutes to save a flow |
STUDIO-3197 |
Datamapper generates an error if a csv has repeated column names |
STUDIO-3190 |
misleading message when reloading metadata on user-defined JSON input |
STUDIO-3189 |
Fixed Width Properties: why 'quote string' option? |
STUDIO-3183 |
Studio crashes with widget disposed error |
STUDIO-3178 |
Manually provided expressions do not render an arrow |
STUDIO-3174 |
Multiple grf editors receive the same close event |
STUDIO-3165 |
Problem with 1.3.x Connectors in Studio 3.4.0 |
STUDIO-3157 |
Assign Input Field to output field does not belong to current mapping generates bad script |
STUDIO-3154 |
Improve version validation between ESB and CCs |
STUDIO-3149 |
Autocomplete doesn’t work with functions arguments |
STUDIO-3148 |
Studio crashes when creating a new project if having more than one runtime installed in Windows |
STUDIO-3145 |
Delete Multiple Fields in the user-defined wizard component |
STUDIO-3138 |
SFDC Connector not retrieving OpportunityLineItem Metadata |
STUDIO-3132 |
DataMapper XML to XML Mapping Does Not Allow You To Finish Wizard |
STUDIO-3129 |
HL7 Message Type list should be sorted |
STUDIO-3128 |
Showing blank image in DataMapper errors logger in Windows 7 |
STUDIO-3122 |
Problem when deleting elements inside the ALL Message Processor |
STUDIO-3084 |
Global elements are being displayed across projects |
STUDIO-3059 |
Http outbound sets method to GET from POST when editing graphical view |
STUDIO-2976 |
Scrip Component is not displaying the script text |
STUDIO-2968 |
Maven: subsequent addition of new components may block because of pom being updated |
STUDIO-2873 |
Dragging Catch Exception Strategy outside of flow causes the name to become empty in the XML |
STUDIO-2849 |
Default engine for Script Transformer and Component is JavaScript; this should be Groovy |
STUDIO-2603 |
Add Processor Chain to the palette |
STUDIO-2492 |
Multiple Runtimes: Unknown node definition when using EE components on a project created with a CE Runtime |
STUDIO-2475 |
Two way editing: problem with soap version attribute |
STUDIO-2456 |
properties-ref in context:property-placeholder is not allowed and silently removed |
STUDIO-2434 |
Maven: I should be able to (maven)build a studio project created with a pom (ee artifacts not published) |
STUDIO-2294 |
Exception Strategy inside choice making trouble |
STUDIO-1971 |
Studio should support spring profiles |
STUDIO-1435 |
Multiple XML validation errors in Studio editor |
STUDIO-716 |
Flow properties description text box looses the tabulation given when changing to XML configuration |
Mule Management Console
Issue | Description |
---|---|
MP-299 |
On Rest API, when listing flows, password information is shown for secure protocols (eg sftp). Hide password for secure endpoints. |
MP-275 |
SFTP endpoint shows details about user and password. Hide password for secure endpoints. |
MP-295 |
SFTP username and password visible in plain text in MMC. Hide password for secure endpoints. |
MP-290 |
Business Event Analyzer truncating values. Make length of exception details for business events larger (and configurable). This is meant to be a bit hidden anyway, so we don’t risk people using extremely large values |
EE-3025 |
Agent port range capability does not work on Windows. Fix the way port bindings work under Windows. |
n/a |
Stop alert watchers on agent stop. This is an improvement on how resources are managed when dealing with alerts. |
n/a |
Fix jetty connector timeout case when reusing same connector causing it to wrongly succeed on second open attempt. |
SE-75 |
Deployment actions are always logged as System in the MMC audit log. Use logged in user instead of current user, which may be a privileged token, for logs. In the Audit Log deployment actions are now logged as the user who triggered them instead of the system user. |
SE-133 |
Cannot compare with Boolean JMX Attribute. Consider Boolean attribute for JMX alert. Defining alerts based on boolean attributes now works properly. |
SE-34 |
In Mule application embedded deployments, when clicking on a flow in MMC, an error occurs. Fix Flows tab for embedded Mule ESB. It allows clicking on flows in the flow tab to get further details. |
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.3.3. Contact MuleSoft if you have a question about a specific module.
Migrating from Mule ESB 3.3.2 to 3.3.3
The improvements and fixes that Mule ESB 3.3.3 introduces require no specific migration activities for Mule ESB, Mule Studio, Mule Management Console, or Mule DevKit.
Known Issues
-
If an input stream is used as a payload and combined with clustering, when the processing goes from one node to the other, in Mule 3.3.0 the stream truncates and in Mule 3.3.1 an exception is thrown.
-
Sending JMS messages between Mule 3.3.1 and Mule 3.2.1 doesn’t work because the Mule session header encoding is incompatible between the two. Add a LegacySessionHandler to make this work.