Mule exceptions do not halt process execution

Details

  • User impact:
    Medium
  • Similar Issues:
    None

Description

When a process sends a Mule message and an exception occurs (e.g. in the service or transformer), this exception gets handled by Mule and does not get "bubbled up" to the process, so the process execution happily continues along, not aware that an exception occurred.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Travis Carlson added a comment -

The problem is in ProcessMessageReceiver.generateEvent(). If the message is sent via routeMessage() (which is the default behavior), the ExceptionPayload is not set on the response message. Setting allowGlobalDispatcher = true will use MuleClient.send() instead, which does set the ExceptionPayload and makes the test case pass. However, this leads to a concurrency issue under high load which makes the Loanbroker BPM test case fail.

If the concurrency error could be fixed, then I would just remove the routeMessage() and make the send() behavior the default. Maybe we'll get lucky and this will just go away after some of the 3.0 cleanup.

Show
Travis Carlson added a comment - The problem is in ProcessMessageReceiver.generateEvent(). If the message is sent via routeMessage() (which is the default behavior), the ExceptionPayload is not set on the response message. Setting allowGlobalDispatcher = true will use MuleClient.send() instead, which does set the ExceptionPayload and makes the test case pass. However, this leads to a concurrency issue under high load which makes the Loanbroker BPM test case fail. If the concurrency error could be fixed, then I would just remove the routeMessage() and make the send() behavior the default. Maybe we'll get lucky and this will just go away after some of the 3.0 cleanup.
Hide
Permalink
Mateo Almenta Reca added a comment - - edited

Has this gone away for 3.0 CE?

Show
Mateo Almenta Reca added a comment - - edited Has this gone away for 3.0 CE?
Hide
Permalink
Travis Carlson added a comment -

MuleClient.send() is now the default behavior, "allowGlobalDispatcher" attribute has been removed.

http://fisheye.codehaus.org/changelog/mule/?cs=19390

Show
Travis Carlson added a comment - MuleClient.send() is now the default behavior, "allowGlobalDispatcher" attribute has been removed. http://fisheye.codehaus.org/changelog/mule/?cs=19390

People

  • Assignee:
    Travis Carlson
    Reporter:
    Travis Carlson
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: