activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: Load Balancer configuration
Date Wed, 11 Apr 2007 18:16:47 GMT
Could you run with 4.1.1 in a profiler to see where the memory is
being used? Incidentally I wonder if 4.2-SNAPSHOT has this issue?

On 4/11/07, Dhawan, Vikram (LNG-DAY) <vikram.dhawan@lexisnexis.com> wrote:
> I see it in AMQ4.0.1 and AMQ4.1.1 both.
>
> Thanks!
>
> Vik
>
> -----Original Message-----
> From: James Strachan [mailto:james.strachan@gmail.com]
> Sent: Wednesday, April 11, 2007 2:13 PM
> To: dev@activemq.apache.org
> Subject: Re: Load Balancer configuration
>
> On 4/11/07, Dhawan, Vikram (LNG-DAY) <vikram.dhawan@lexisnexis.com>
> 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/
>


-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message