Version 1.3.2
Build
201212121942 (EE)
Build
201212121943 (CE)
December 10, 2012
MuleSoft is pleased to announce the release of Mule ESB 3.3.2 which offers improvements to the Mule Management Console and further stabilizes Mule ESB.
These release notes apply to the Enterprise Edition of Mule ESB 3.3.2. We have applied all of the core changes in 3.3.2 runtime to the Enterprise Edition.
Download Mule ESB 3.3.2 Enterprise Edition to take advantage of an improved and hardened Mule ESB.
December 10, 2012, v1.0 Initial Publication
December 11, 2012, v1.1 Added items to list of Mule ESB fixed issues; added known issue
December 17, 2012, v1.2 Added Build Numbers for released products.
December 18, 2012, v1.3 Added list of DevKit Fixed Issues
January 25, 2013, v1.4 Added items MP-142 to list of ESB Fixed Issues
February 19, 2013, v1.5 Adjusted versions of Connectors released with version 3.3.2.
Enterprise Edition | Community Edition | |
---|---|---|
ESB |
Build 20165 |
|
Studio |
Version 1.3.2 201212121942 (EE) Build 201212121943 (CE) |
|
Management Console |
Build 6986b41e51 |
|
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 |
The following list details the improvements to the Mule Management Console.
Mule applies versions to applications when deployed on the Mule Management Console.
The Mule Management Console offers an improved application deployment status.
The Mule Management Console presents a screen in which a user can determine, at a glance, the deployment location and status of each application (including deployed apps that are, in fact, not in the target server).
Mule Management Console includes information about deployment operations in the Audit Logs.
For most use cases, Mule ESB 3.3.2 does not change the hardware and software system requirements established by Mule ESB 3.3.1.
Please contact MuleSoft with any questions you may have about system requirements.
This list covers some of the known issues with Mule ESB 3.3.2. Please read this list before reporting any issues you may have spotted.
EE-2994 |
populate_m2_repo is retrieving unnecessary jars and missing necessary jars |
Enterprise Edition
MP-76 |
Old version of the agent is unable to pair to the Console because of SSLHandshakeException. |
MP-102 |
Flows info for clusters is the same for every cluster when using the same application |
MP-167 |
Setting enableDiscovery=false still creates jmDNS* threads |
MP-188 |
Deployment unreconciled status is incorrectly shown after newly created deployment which was saved but never deployed. |
MULE-6548 |
PGP is not closing the stream when ends the encryption |
MULE-6537 |
Improve Multicast handling with several mule servers |
MULE-6535 |
Flow loses invocation variables added after returning from sub-flow when calling exception strategy |
MULE-6534 |
Catch-exception-strategy’s expressions fail to filter exceptions |
MULE-6531 |
Put AspectJ Weaver dependency back in the distribution |
MULE-6527 |
Exception when calling DeploymentService#undeploy on a stoppedapp |
MULE-6524 |
MEL ClassCastException with function |
MULE-6516 |
MEL xpath function does not reset the message payload when the original payload is a stream |
MULE-6492 |
NullPointer Exception in org.mule.routing.EventGroup.addEvent when running in a cluster |
MULE-6491 |
HTTP/S transport does not reuse connections |
MULE-6488 |
JmxAgent - Infinite loop when undeploying an app if it has a flow with a name that includes the character ':' |
MULE-6486 |
MVELExpressionLanguageContext retains payload instance |
MULE-6484 |
MulePropertyEditorRegistrar causing performance issues when generating dynamic endpoints concurrently |
MULE-6472 |
Missing event initialization on AbstractAsyncRequestReplyRequester |
MULE-6453 |
Wrong junit version in cep example |
MULE-6426 |
payload-type-filter not allowed within collection-aggregator-router since mule 3.x |
MULE-6400 |
IdempotentRedeliveryPolicy does not rely on Mule object store manager to create an object store |
MULE-6385 |
When working offline Mule 3.3 can not resolve schema locations using 3.2 urls |
MULE-6197 |
overwrite SFTP strategy doesn’t work |
MULE-6183 |
DynamicOutboundEndpoint.createStaticEndpoint is marked as synchronized and causes congestion under high load |
MULE-5776 |
Jetty and Ajax transport do not extend correct schema type and are therefore missing various configuration options |
MULE-5232 |
xslt-transformer uriResolver setting does not work |
MULE-4209 |
Embedded distribution has no version info in MANIFEST and so startup splash screen does not show version info |
EE-2842 |
When working offline Mule 3.3 can not resolve schema locations using 3.2 urls |
EE-2829 |
AbstractCSVTransformer - use IOUtils.getResourceAsString to pick up the mappingFile |
EE-2822 |
JDBC EE Outbound endpoint, loss of session properties when outbound endpoint is request response |
MULE-6549 |
jBPM, MuleSendActivity.perform is not thread safe |
EE-2964 |
Mule cannot find AspectJ’s classes even though they are in the app’s lib/ folder |
EE-2989 |
Add missing tanuki wrapper libs to support S/390 |
MULE-6552 |
XMPP doesn’t support dynamic endpoints |
MULE-6557 |
Performance regression when caching JMS Sessions |
MULE-6561 |
NullPointException when using splitter/aggregator |
MP-142 |
When deleting old deployment the new deployment apps are undeployed |
STUDIO-2440 |
Character ' (single quote) is not being generated well |
STUDIO-2446 |
Connectors are not generating the XML code for the Reconnection Strategy |
STUDIO-2454 |
escaped expression are unreadable |
STUDIO-2485 |
Upgrading to Latest Mule Studio causes single quotes to be escaped in XML |
STUDIO-2489 |
We need to change the UI for Maps (used in Connectors) |
STUDIO-2524 |
JDBC EE highlights the query-ref when the query is defined in another file. |
Enterprise Edition
MP-215 |
On Application screen, apps from undeployed deployment should not be displayed. |
MP-206 |
REST API: When adding applications to a deployment, it allows passing an application id, when the id passed should be the application version id. |
MP-198 |
When newly create deployment is saved, it is also deployed. |
MP-196 |
On Rest API, NPE when updating server without providing name param. |
MP-190 |
Error when updating never deployed deployment. |
MP-189 |
Deployment unreconciled status is incorrectly shown after applying changes on existing deployment. |
MP-187 |
Deployment created with apps with spaces on name and/or version fails to be deployed. |
MP-186 |
When deleting deployment, all apps defined on the deployment will be removed from target |
MP-185 |
Inconsistent and incomplete validation messages when saving modified deployments |
MP-182 |
Changing the deployment and clicking on “Apply changes” triggers reconciliation on targets. |
MP-181 |
Create User actions when deployment is edited. |
MP-179 |
Create User actions when deployment is created. |
MP-178 |
When newly create deployment is saved, it is also deployed. |
MP-177 |
Unable to add application to a deployment |
MP-176 |
Saving deployment to offline server showing error message but still saving it |
MP-171 |
Deployment unreconciled status is incorrectly shown after newly created deployment which was saved but never deployed. |
MP-170 |
Deployment unreconciled status is incorrectly shown after taking the target of the deployment offline. |
MP-168 |
Deletion of deployment descriptor in the deployment view of the Applications tab remains loading forever |
MP-163 |
Remove confusing 'reconciled' state |
MP-159 |
On 3.4 branch, modify distribution generation to not include the agent mule app on the bundle. |
MP-158 |
Create 3.4 branch with actual 3.3.2-SNAPSHOT contents. |
MP-155 |
When uploading a file on the repo, check for invalid characters on the name and on the version. |
MP-154 |
With new version strategy, deploy fails due to invalid char in the OOTB timestamp. |
MP-150 |
Sonar goal fails to be executed on Bamboo. |
MP-149 |
Error when undeploying stopped app. |
MP-148 |
Inconsistent behavior when trying to deploy to empty Server Group from New deploy form or from deployments view. |
MP-144 |
State of a deployment is no correctly refreshed among concurrent users. |
MP-141 |
If the deployment name contains the char ':' the mmc data get corrupted |
MP-140 |
On Dashboard, duplicate unreconciled icon on Deployment Status portlet. |
MP-135 |
Add test coverage for managing files remotely using Rest API |
MP-113 |
On Deployments, specifying a specific page when results are pages is very difficult to do due to refresh times (2 secs) |
MP-112 |
On Deployments, when a checkbox is checked to select a deploy, checkbox sometimes cannot be unchecked. |
MP-107 |
Timestamp format on error message returned by Rest update is incompatible with lastModified format used on queries. |
MP-103 |
After using the deployment descriptors several times, it’s not possible to undeploy an application |
MP-100 |
Revisit Master QA plan. Update priorities. |
MP-98 |
On Deployments, when a checkbox is checked to select a deploy, checkbox is unchecked 2 seconds later. |
MP-84 |
MMC Log Regex Alerts fail when the log file is rolled |
MP-77 |
Error accessing AlertService#getAlerts |
MP-69 |
The MMC Agent is using an expired certificate |
MP-61 |
Fix sporadic integration tests failure |
MP-60 |
The console that pairs with the agent should be the only client that can make calls to the agent |
MP-54 |
Document MMC Rest |
MP-53 |
Agent - add the ability of disabling weak ciphers on Jetty |
MP-51 |
System allows that 2 or more Consoles control the same agent at the same time. |
MP-48 |
As an MMC user I expect to view the flows recently added by other users without refreshing, so I don’t have to manually refresh the page all the time. |
MP-46 |
As an MMC user I expect to view the deployments recently created by other users without refreshing, so I don’t have to manually refresh the page all the time. |
MP-45 |
As an MMC user I want to be notified when another user modified the deployment I’m viewing so I can decide whether I want to continue with my changes or abandon them |
MP-44 |
As an MMC user I want to be notified when another user deleted the deployment I’m viewing, so I can decide whether I want to create a new one or abandon my changes. |
DEVKIT-285 |
Using @Inject along with @RequiresEnterpriseLicense fails with compilation error |
DEVKIT-281 |
java.lang.Class not supported in Studio plugin generation |
DEVKIT-280 |
Generated code for reconnection strategies in connectors is invalid |
DEVKIT-279 |
ConnectionManagerKey equals implementation relies on identity (==) comparison |
DEVKIT-278 |
only first generic type is passed to the connection manager |
DEVKIT-276 |
Complete Studio editor support for new OAuth improvements |
DEVKIT-275 |
Studio plugin generator improvements for 3.3.2 |
DEVKIT-274 |
Initialize failt when Mule ESB version is not standard |
DEVKIT-272 |
Not able to build connector with complex type |
DEVKIT-270 |
Nested elements in editors.xml Studio file contain final static constants |
DEVKIT-251 |
Error building documentation in bamboo |
DEVKIT-236 |
When a connector has exactly two processor methods Studio shows a checkbox 'Operation' instead of the usual drop-down menu |
DEVKIT-227 |
Rest client verifier is not throwing the right exceptions when checking for getters existence |
DEVKIT-226 |
@RestHeaderParam with complex type should call param.toString |
DEVKIT-225 |
Project builds OK but fails when creating Studio update site |
DEVKIT-185 |
accessTokenId attribute edit field is not generated in studio plugin for Oauth2 |
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.2. Contact MuleSoft if you have a question about a specific module.
The improvements and fixes that Mule ESB 3.3.2 introduces require no specific migration activities for Mule ESB, Mule Studio, Mule Management Console, or Mule DevKit.
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.
Please refer to the following resources for assistance using Mule ESB 3.3.2.
Access MuleSoft’s Forum to pose questions and get help from Mule’s broad community of users.
Enterprise Edition To access MuleSoft’s expert support team, subscribe to Mule ESB Enterprise Edition and log in to MuleSoft’s Customer Portal.