I would say you can profile any other java application and the profiler will give you the suspect classes that may leak memory in. As messages come and go, there are many instances in the heap and this seems reasonable. If your application leaks memory I will possibly believe. We have run ActiveMQ 5.5 in production for years(7 X 24) and it has been working well.
At 2013-04-19 00:01:12,mvilleta <[email protected]> wrote: >Good Afternoon, > >I'm a new user of JMS technology and particularly with ActiveMQ solution. >I'm having some problems with the performance of my application. >Specifically, i'm developing a 24x7 application. We are using >MessageListener for all consumers. > >Doing performance and continuity tests I detected memory leaks in certain >ActiveMQ classes. After passing a profiler tool, I saw a large amount of >ObjectMessage and Message instances. Trying to improve my performance >problems, I decided to use "clearBody" and "clearProperties" methods, and I >after passing again the profiler tool, I noticed, that the memory leak grows >slower. Does it have any sense?. > >We are not closing the session and the conexion instances because we reuse >them all the time. > >Thank you in advance, > >Regards > > > >-- >View this message in context: >http://activemq.2283324.n4.nabble.com/Question-about-listeners-performance-tp4666024.html >Sent from the ActiveMQ - User mailing list archive at Nabble.com.
