Hi Mark, There is a memory leak solved in the 5.3.1 branch ( AMQ-2448<https://issues.apache.org/activemq/browse/AMQ-2448> ) that occurs when using network of brokers. It doesn't seem it's exactly your test case, as the two brokers are apparently up during your test. Maybe you give a try to the 5.3.1 trunk version and check if you still have the memory leak.
If this doesn't solve your problem, a code sample reproducing the memory leak would be useful. Thank you very much, Seb On 4 February 2010 08:26, mark.w <m.wu...@googlemail.com> wrote: > > Hi, > I have a following test scenario: I start two brokers (ver. 5.3.0) on local > host on two different ports, lets say broker A on port 61616 an B on 61617. > In broker A I configure additionally a networkConnector with > uri="static://(tcp://localhost:61617)". > If both instances are started I run a unit test that creates a topic > subscription to B and close the connection afterwards. > > I noticed that in broker A (create a heapdump and analyze it with MAT) > after > each test run two objects of type org.apache.activemq.command.ConsumerInfo > (in the destination.physicalName I see my topic) stay for ever. > I tried also to set dynamicOnly=true option, but it does not change the > behavior. > > Is this a known memory leak? > > Thanks in advance and best regards, > Mark > > > -- > View this message in context: > http://old.nabble.com/Memory-leak-while-running-a-network-of-brokers--tp27445873p27445873.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- Sebastien Rodriguez
