Streams are not closed if mule exceptions occur in AsbtractMessageReciever

Details

  • User impact:
    Low
  • Effort points:
    1
  • Similar Issues:
    None

Description

An example of this is if there is an unexpected exception while processing endpoint filter.. exception is thrown but stream will not be closed.

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MULE-2499 No way to close streams (and release connections) if an exception occurs outside of the MessageDispatcher

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ross Mason added a comment -

Does the exception get handled by the Exception strategy for the component or the connector?

Show
Ross Mason added a comment - Does the exception get handled by the Exception strategy for the component or the connector?
Hide
Permalink
Daniel Feist added a comment -

As far as I remember it gets handled by the connector exception strategy but because the event has not yet been set in the EventContext the exception strategy doesn't have access to it and so can't close it.

Show
Daniel Feist added a comment - As far as I remember it gets handled by the connector exception strategy but because the event has not yet been set in the EventContext the exception strategy doesn't have access to it and so can't close it.

People

  • Assignee:
    Unassigned
    Reporter:
    Daniel Feist
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: