Hi,
Just a quick heads up on an issue I had a quick look into this morning
and to see if anyone has any good ideas ...
http://mule.mulesource.org/jira/browse/MULE-2158(The issue is reported against 2.x but it's likely it also affects 1.4.x.)
This issue was initially reported as a memory leak which appeared when
performing stress testing as part of MulticastRouterMule2136TestCase
test case. After looking into this memory leak, I found that there is
no bug and this seems to be expected behaviour.
The reason for this is that there are outbound vm endpoints with event
queuing enabled that have no vm receiver configured with the same uri,
and neither does any client code pull events from the queue via the
dispatcher (using recieve()/request()). The result of course is that
these message just pile up in the MessagePersistenceStrategy's hashmap
until we get a OutOfMemoryException.
(MemoryPersistenceStrategy is used by default at least in 2.x)
The question is what should be done about this:
- nothing. it's expected
- nothing. it's expected, but document somewhere.
- it's expected, but we need better error/warn messages so user
doesn't get a OME or if they do then know why they are getting (how
would we do this?).
- set up a dummy receiver if none configured? ( not sure this would
work though because of the receive() usage)
Dan
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
