Mule ESB 3.3.0 Release Notes

MULE-6273

Exception Strategies are not being invoked in a flow with an Ajax inbound endpoint.
Workaround: Enclose flow logic in a flow invoked by VM.

MULE-6258

Request-reply outbound endpoint sends reply to caller temp queue instead of self temp queue
Workaround: None

MULE-6209

Referencing "exception" inside a groovy script should return null if there were no exception thrown
Workaround: Use exceptionPayload.

MULE-6165

Null' is used both as a response from message processors with no result and to signify a message dropped by a filter
Workaround: None

MULE-6094

RestServiceWrapper
Workaround: A patch has been applied to resolve the issue.

MULE-6060

Do not always serialize Mule session security context
Workaround: None

MULE-6058

Cannot override the JsonTransformerResolver
Workaround: None

MULE-6046

Incorrect checking for supported transformer types in DefaultMuleMessage
Workaround: None

EE-2756

Cache stores intermediate payload of aggregators instead of final payload contents
Workaround: None

EE-2700

HTTP Polling on a cluster: all nodes poll independently
Workaround: Poll using Quartz.

EE-2699

EE-2695

Creating/disbanding clusters repeatedly in a short period of time causes them to shutdown
Workaround: Avoid recreating the cluster repeatedly.

STUDIO-1217

When you configure any of the JDBC datasources (MySQL, Oracle, etc.), the driver is not added.
Workaround: Add the driver manually by right-clicking on project root > Build Path > Add External Libraries > Browse; then add the corresponding . jar file.

STUDIO-1077

Neither the HTTP nor HTTPS Polling Connectors can be referenced using the Properties pane in the Message Flow view.
Workaround: Make the reference using the XML configuration view by adding this: ref="HTTP_Polling".

STUDIO-866

When you remove a Request-Response endpoint or replace it with a one-way endpoint in the Message Flow view, the response element is not removed from the XML configuration file.
Workaround: Delete the Response element manually from the configuration file using the XML editor.

STUDIO-459

Unable to add a response element when creating a second flow within a single .mflow file.
Workaround: Add the response element manually in the XML configuration.

For request-response endpoints embedded in a composite source within a subflow, icons do not show the proper exchange pattern.
Workaround: This is only a matter of visual aesthetics within the graphical interface; if you set the correct exchange pattern through the Properties pane, the flow should work as intended, despite appearances on the Message Flow canvas.

STUDIO-162

The Description field is not persisted when you switch back and forth between the Message Flow and XML configuration views. This issue may appear in the bundled examples that are included in Mule Studio. Currently, there is no way to populate the Description field using the graphical interface.
Workaround: Once the application is complete and you are sure that you no longer need to use the Message Flow view, copy the description and insert it into the configuration file using the XML editor.

When you create a project from an existing template, the Problems pane may display errors such as the following:
"Unable to find type 'org.ordermgmt.OrdersView' on build path of project order_f”
Workaround: From the main menu, navigate to \{\{Project > Clean…​ }}, then select clean all projects. This re-compiles all your projects, so that these errors no longer appear.

When you install the Windows 64-bit version of Mule Studio with the IBM JDK, then create a project using the Order Discounter template, the Problems pane may display errors such as the following:
"Attribute key is not defined as a valid property of object Element:Objects is not allowed to be child of element Object"
Workaround: Ignore the errors and run your application. It will run successfully.

STUDIO-1212

Response section in the Composite Source is not being reflected in the canvas.
Workaround: None

STUDIO-280

When using eGit and committing Mule projects, usually one or more of src/(main and test) or (java and resources) will be empty and therefore ignored by git.
Workaround: reload the workspace/restart Studio. Studio will generate the missing directories this way (and will show as untracked files).

STUDIO-1835

Generate WSDL in the SOAP component works with CXF version 2.1.3, instead of using 2.5.1. This can cause the loss some part of the WSDL generation.
Workaround: None

STUDIO-1920

There are backwards compatibility issues with the evaluator attribute when using expressions, as STUDIO supports only the latest version of the ESB, version 3.3. If you attempt to use the expression evaluator attribute, it will be marked as an error.
Workaround: use the new MEL (Mule Expressions Language) format adding the evaluator prefix before the expression.

STUDIO-1953

DataMapper - Complex XMLs. Need the ability to handle nested and recurring elements in the XML.
Workaround: None

STUDIO-1954

DataMapper - Need support for custom Java Functions.
Workaround: None

STUDIO-1955

DataMapper - Need support for multiple input sources that maps to multiple output sources.
Workaround: None

STUDIO-2001

DataMapper - Need ability to map for XML.Any elements.
Workaround: None

-1237

Business Event Analyzer: only custom events are displayed on transaction details if HttpRequestToNameString is used.
Workaround: Change “Doc:name” to something different from the flow name.
<flow name="HelloWorld" doc:name="HelloWorld2" tracking:enable-default-events="true">.
Enable events on transformer elements as needed and, optionally, remove doc:name (in order to avoid overwriting the flow doc name):
<transformer ref="HttpRequestToNameString" tracking:enable-default-events="true"/>

-1234

Restarting one cluster restarts all the clusters that have been configured.
Workaround: None

-1208

A cluster can only be disbanded if all nodes are running.
Workaround: None

-1205

Flow information for clusters is the same for every cluster when they are all using the same application.
Workaround: To view the correct flow information, select each cluster individually through the left-hand menu panel.

-1199

When you create a cluster, not all the applications deployed to the server group get properly removed.
Workaround: Before creating a cluster, undeploy all applications from the cluster nodes, then remove the nodes from your server group.

-1198

Post Process Notifications for "one-way" endpoints are not being registered, which causes Business Events to be marked as failed.
Workaround: None

-1165

In the Business Events tracker, incorrectly reports the name of the flow associated with a given exception strategy. Specifically, when a message jumps from flow A to sub-flow B, then returns to Flow A, and a component throws an exception in Flow A, the Business Events list Flow A’s exception messages under Flow B’s name.
Workaround: None

MULE-6275

on-redelivery-attempts-exceeded does not support doc:name attribute

MULE-6248

Session variable gets lost if using an enricher

MULE-6247

Custom transformers are not registered on mule context

MULE-6240

TransactionalQueueManager loads all keys from all ListableObjectStores in order to populate internal message queues

MULE-6236

Unable to set content-type on RestServiceWrapper

MULE-6234

Cannot use QueuePersistenceObjectStore on UntilSuccessful

MULE-6203

Transport archetype creates test using deprecated methods

MULE-6199

Attributes name for basic functionality is optional but should be required

MULE-6189

Failed to initialize app. MBean Exception.

MULE-6182

WS-Security element should not support Validators and Security Manager if the CXF MP is a client

MULE-6176

Expression evaluators that can be used in filters only fail with obscure error messages if used in no valid places

MULE-6169

expression-component does not allow variable declaration

MULE-6163

Endpoint response message processors should not be processed when an endpoint doesn’t have a response

MULE-6162

AbstractMessageReceiver returns value even when endpoint exchange pattern is one-way

MULE-6159

Proxy Service fails with NPE when the WSDL has Faults defined

MULE-6156

AttributeEvaluator does not support parentheses inside expressions

MULE-6146

Filters in sub-flows do not filter as expect and should (rather only act as sub-flow 'return')

MULE-6137

Missing implicit conversion for converters

MULE-6128

DefaultInboundEndpoint flowConstruct has setter but no getter

MULE-6127

Default mule application mule context is private

MULE-6102

VM Queue not picking up messages previously persisted in the queuestore directly

MULE-6082

Application Deployment Descriptor is not properly closed

MULE-6066

Default Exception Strategy ignored with CXF component

MULE-6051

XA transactions causing an increment in ActiveMQ consumers

MULE-6050

When a Mule object (application, connector, flow, endpoint, etc.) is stopped more than once, the second and later stops have no effect

MULE-6047

Application of a transformer chain to a mule message can produce different return types

MULE-6028

activemq-xa connector does not reconnect to JMS provider once disconnected

MULE-6019

Transactions on one-way vm queues causes CPU to go warm

MULE-6017

spring.handlers and spring.schema are not generated correctly within the embedded distribution

MULE-6007

Application fails to start when using until-successful router with a persistent ObjectStore

MULE-6004

Commit on exception strategy JMS, FILE and FTP are transport are not consuming the message

MULE-6003

CXF swallows exceptions in flows, prevents exception strategies from processing exceptions

MULE-5998

As from 3.2 aggregators no longer maintain the order events are received when creating MuleMessageCollection

MULE-5997

Inconsistent definition of some expression evaluators

MULE-5988

ConcurrentModificationException during serialization of MuleSession with SessionHandler if there is a non-serializable property

MULE-5981

Keystore type configuration is incorrect

MULE-5965

Mule throws EOFException when it finds an empty message within a queue store

MULE-5919

Reply-To doesn’t work for WMQ transport

MULE-5907

ReplyTo property is lost because is not properly propagated between events

MULE-5884

ActiveMQ web documentation should explain activemq jar inclusion in lib directory

MULE-5827

File connector in 3.2.0 ignores #[header:originalFilename] and writes no file

MULE-5825

JDBC DataStore requires that the JDBCConnector has the queryTimeout set to work

MULE-5797

TransactionalQueueManager is only started after inbound endpoints/sources - Duplicate events can appear in SEDA queues

MULE-5617

Javadoc no longer generated with Maven 3 build

MULE-5415

Http transport doesn’t work for first invocation

MULE-5379

http endpoint port attribute does not support expressions

EE-2747

Hazelcast cluster stops consuming messages after node restart

EE-2738

Failure to create implicitly chains of 2 or more Transformers

EE-2737

Mule should not use default user exposed object store for internal purposes.

EE-2727

Default app config in standalone distribution refers to 3.2 XML schema

EE-2725

Soak test fails after 15 to 25 minutes, with multiple resources locking on to ActiveMQ resource

EE-2724

Batch update forces Map payload when that is not needed

EE-2721

Configuring a Consumable Filter doc for Cache Message Processor is missing

EE-2720

muleContext.getClusterNodeId() is always 0

EE-2701

NPEs in logs while raising nodes

EE-2697

Polling + Updating JDBC database throws Connection Closed exceptions, always fails when using services

EE-2691

Application’s lifecycle is applied to global server’s objects

EE-2681

recover() method in TransactionalQueueManager should check for empty keySet from object store

EE-2658

Cannot reference JDBC Object Store using JDBC EE schema

EE-2657

Cannot reference JDBC Datasources using JDBC EE schema

EE-2631

spring.handlers and spring.schema are not generated correctly within the embedded distribution

EE-2609

Mule throws EOFException when it finds an empty message within a queue store

EE-2577

Mule fails to start on HP-UX

EE-2221

activemq-xa connector does not reconnect to JMS provider once disconnected

STUDIO-821

Request Reply (flow control) must have a way from the UI to add inbound and outbound endpoints

STUDIO-991

In the MuleMQ and ActiveMQ widget dialog box, in the MuleMQ properties tab, checking the "XA Support mode" causes the dialog box to go blank for a second

STUDIO-1157

Spring import schema does not have doc:Name attribute

STUDIO-1546

Transactions dialog for VM endpoint is too big

STUDIO-1549

WMQ Endpoint: Exchange pattern should be placed after Display Name

STUDIO-1550

Quartz: duplicated job attribute

STUDIO-1561

HTTP Outbound endpoint: Remove the blank option from the HTTP method attribute

STUDIO-1518

Unable to create a bean - Getting Null Pointer Exception when trying to create a bean in a JDBC connector

STUDIO-1406

Installing a newer Studio version and using an old workspace (the default one) causes errors and the runtime is lost

STUDIO-1388

Getting concurrent modification exception when adding CC and referencing them

STUDIO-1394

Two-way editing issue: Salesforce and Twitter streaming endpoint are parsed as invalid configuration and removed from canvas and then XML

STUDIO-1386

Reconnection Strategies: Add the 'Not use reconnection strategy' option

STUDIO-1332

WMQ XA connector should be considered as a checkbox inside WMQ to be enabled and not a separate connector

STUDIO-1454

Getting JNPE when deploying to iON (now known as CloudHub) not having selected a project

-1226

Server Metrics charts are slow to load even with a single mule instance

-1222

Deployment of new version of Application is not working as expected

-1195

Cannot start Mule 2.2.8 using 3.3/2.2.8 agent, -agent-mule2-impl-3.3.0-RC2-full.jar

-1111

UI becomes unresponsive when trying to save a cron job.

-1107

On Business Event, queries do not show new generated events while agent is on heavy load (if load is reduced situation goes back to normal).

-1059

takes too long to show Deployments (Tab, and portlet)

-1022

On Event Analyzer, Processing Time, using m as time unit is allowed, but system does not process it.

-1016

On Servers tab, if cluster item is clicked in the left side tree panel, the cluster view is not opened.

enforced transformation

A transformer yields an expected type of message payload; the flow must be prepared to manage only one type of output.

A transformer yields one of several possible types of message payload; transformed payload type is unknown and the flow must be prepared to manage several different outputs.

implicit transformation

If a transformer exists to change message payloads from type B to C, and it receives a message payload type A, Mule implicitly looks for a converter that can convert the message payload from A to B, before introducing the message payload to the B-to-C transformer.

If a transformer receives an unexpected type of message payload, it throws an exception.

extended transformer lookup

If a transformer exists to change message payloads from type B to C, and it receives a message payload type A, Mule implicitly looks for a converter that can convert the message payload from A to B, before introducing the message payload to the B-to-C transformer. If Mule cannot find an A-to-B converter, it extends its search to look for combinations of converters that will yield a message payload type B. For example, it may convert a message payload from A to F, then use another converter to change it from F to B before introducing it to the B-to-C transformer.

If a transformer receives an unexpected type of message payload, and cannot find a single converter to match its conversion needs, it throws an exception.