Hi, do you refer to a memory issue in (C++) broker or in Java client? And what version of broker+client do you use?
If you refer to Java client memory issue, did you check Garbage collector logs? Could you add JVM options: -Xloggc:/path/to/gc.log -XX:+PrintGCDateStamps -XX:+PrintGCDetails and wait until Full Garbage Collector occurs (and check the GC log then)? Kind regards, Pavel ----- Original Message ----- > From: "RajendraNPTL" <prr...@gmail.com> > To: users@qpid.apache.org > Sent: Monday, May 12, 2014 6:26:47 AM > Subject: Closing connection with broker is not releasing Memory ? > > Hello, i am using Qpid c++ broker. > > While doing performance test with the Java client, i observed that starting > a connection with broker taking nearly 50 to 60MB. > It's not releasing the memory by closing the connection . It's releasing > memory only after exiting the program. > > Anybody faced the same issue ? > > > > ----- > Time and tide waits for NONE ..!! > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Closing-connection-with-broker-is-not-releasing-Memory-tp7608007.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
