[#MULE-3558] Streams are not closed if mule exceptions occur in AsbtractMessageReciever

Mule

Streams are not closed if mule exceptions occur in AsbtractMessageReciever

Created: 16/Jul/08 08:56 PM Updated: 12/Nov/08 08:59 PM

Component/s:

Core: Exception Handling, Core: Streaming

Affects Version/s:

2.0.1

Fix Version/s:

2.1.x Backlog

Time Tracking:

Not Specified

Issue Links:

Related

This issue relates to:

~~MULE-2499~~ No way to close streams (and release connections) if an exception occurs outside of the MessageDispatcher

Labels:	20-streaming
User impact:	Low
Effort points:	1

Description

« Hide

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

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Ross Mason added a comment - 04/Sep/08 12:46 AM

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

[ Permlink | « Hide ]

Daniel Feist added a comment - 04/Sep/08 02:24 PM

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.