Reusing the Jms resources such as sessions, producers is a good practice but not for consumers. Reusing consumers can bring in message stuck problem and you can take a look at http://activemq.apache.org/what-is-the-prefetch-limit-for.html You can use activemq-pool to them handily.
At 2013-04-22 19:34:05,mvilleta <[email protected]> wrote: >Thanks for your answers, > >I continue having the same problem. Reading the API specifications of >"close" method for MessageConsumer and MessageProducer, I noticed that it >specifies the following: > >"Since a provider may allocate some resources on behalf of a MessageProducer >outside the JVM, clients should close them when they are not needed. Relying >on garbage collection to eventually reclaim these resources may not be >timely enough." > >At all my application, I'm never close the sessions of my producers and >consumers. Could it be a performance problem for the application?. > >SouNayi, have you ever closed any session at your 24x7 application >eventually, on that case, how can I do it without stop the service?. > >Thanks in advance > >Regards > > > >-- >View this message in context: >http://activemq.2283324.n4.nabble.com/Question-about-listeners-performance-tp4666024p4666108.html >Sent from the ActiveMQ - User mailing list archive at Nabble.com.
