activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim_Cross <jimcross1...@googlemail.com>
Subject Re: Server side memory leak on connection with NMS
Date Wed, 20 Jun 2007 14:04:41 GMT

OK, so I hooked up JProbe to an instance running on my Windows XP
workstation, and I see the same behaviour.
It looks very much like the InactivityMonitor class is holding on to
instances of TcpTransport - when I release the reference from
InactivityMonitor to TcpTransport in JProbe, it can be garbaged collected
fine.

Is there any way I can completely disable the InactivityMonitor? I tried
using a URL of tcp://localhost:61616?wireFormat.maxInactivityDuration=0, but
got an NMSException saying property maxInactivityDuration does not exist on
WireFormatInfo.


Jim_Cross wrote:
> 
> Hi,
> 
> Further to my earlier message, I realised I'd left out two vital bits of
> information:
> 1. I'm using NMS
> 2. Part of my test app is to have a consumer disconnect fully (close and
> dispose consumer, session, and connection) then reconnect
> 
> A bit more investigation has revealed that if I don't start the consumer
> side, but do hit the server with loads of messages, memory use stays
> stable, under 15mb.
> However, if I just start the consumer side, memory use increases over
> time.
> 
> I'm fairly sure the connections are being closed properly, as the consumer
> count seen in JConsole always shows the correct number.
> 
> Does anyone know why this happens?
> I've seen some messages mentioning mixing ActiveMQ versions can cause
> memory leaks. Could this be the cause? I'm using NMS with ActiveMQ 4.1.1.
> 
> Any help much appreciated.
> 
> Jim
> 
> 

-- 
View this message in context: http://www.nabble.com/Server-side-memory-leak-on-connection-with-NMS-tf3946774s2354.html#a11214106
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message