On 4/11/07, Dhawan, Vikram (LNG-DAY) <[EMAIL PROTECTED]> wrote:
Hi James,
Thanks for your help and suggestion here. But this brings another
concern.
There is always a possibility that some one can write a client app which
connects to AMQ on any of the real AMQ ports (61616/61613/61617 in
sample configuration) and disconnects the same way as Load Balancer is
doing. And what appears to me is this will cause AMQ to throw exceptions
like following, and which will result AMQ going out of memory.
That exception looks fine to me.
ActiveMQ should be reclaiming any memory for bad connections -
exception stack traces don't use up any RAM. If you're seeing a memory
leak then its a bug. Which version do you see this in?
--
James
-------
http://radio.weblogs.com/0112098/
