« Return to Thread: VM memory leak or expected functionality

Re: VM memory leak or expected functionality

by Daniel Feist :: Rate this Message:

Reply to Author | View in Thread

To "just eat the event":

- You would need to be able to detect (at startup? in runtime?) that  
this will happen and then put something in place to eat it.

- You would not be taking into account the receiver()/request()  
usage.  Because even though there is no consumer/receiver configured a  
receive()/request() could be performed at anytime programatically via  
MuleClient or other, and if you have already eaten the event, the  
client code isn't going to get anything.

Dan


On 10 Dec 2007, at 16:22, Holger Hoffstätte wrote:

> Daniel Feist wrote:
>> Yes, the testcase is failing with OutOfMemoryException because it  
>> has an
>> outbound endpoint with no consumer.
>>
>> I just wanted to throw out the more general question of what to do in
>> these situations, if anything...
>
> IMHO just eat the event.
>
> -h
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>    http://xircles.codehaus.org/manage_email
>


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

 « Return to Thread: VM memory leak or expected functionality