On Fri, Nov 27, 2009 at 3:01 PM, titexe <tit...@yahoo.fr> wrote: > > thank you claus, it is to help each other, > > I take this opportunity to thank you for the book "Camel in Action" >
Welcome the book is for Camel, not for me. We value community over code at Apache. The book is just for much better documentation and help others get started with Camel and improve the overall community around Camel. > If not for the problem I will try to remove stream cache > Stream cache? In terms of the JMS problem, can you maybe write a bit more what you are using? Sorry if that was in the start of the mail. Which JMS Broker are you using? Which Spring .jars are you using? What does you route look like? How how you configure the connection to the JMS broker? > Thank you > > > Claus Ibsen-2 wrote: >> >> On Fri, Nov 27, 2009 at 12:03 PM, titexe <tit...@yahoo.fr> wrote: >>> >>> bizarre, even by putting maxMessagesPerTask, the problem is not solved, >>> every >>> second I have a thread that add, and it : >>> >>> ActiveMQ Session ID: Server-1997-XXXXXXXXXX >>> >>> I don't understand anything? >>> >> >> You are probably not caching the session etc. so it may force spring >> jms to recreate a new session all the time. >> >> >> >>> Thank you in advance, >>> >>> titexe >>> >>> >>> Claus Ibsen-2 wrote: >>>> >>>> On Fri, Nov 27, 2009 at 11:43 AM, titexe <tit...@yahoo.fr> wrote: >>>>> >>>>> Thank you for your reply : >>>>> >>>>> I tested this expression and it does not work, it generates me an error >>>>> that >>>>> not recognize this URI: >>>>> >>>>> <from uri="jms:queue:foo&maxMessagesPerTask=-1"/> >>>>> >>>>> I think we should use this : >>>>> >>>>> <from uri="jms:queue:foo?maxMessagesPerTask=-1"/> >>>>> >>>>> What do you think? >>>>> >>>> >>>> Yes. >>>> Its standard URI options so if only have ONE parameter then use ? to >>>> indicate the first parameter. >>>> >>>> If you have TWO+ parameters then use & to separate those. >>>> And if you do that in a XML file then you must escape & so it become >>>> & >>>> >>>> >>>> >>>> >>>>> Thank you >>>>> >>>>> titexe >>>>> >>>>> <from uri="jms:queue:foo&maxMessagesPerTask=-1"/> >>>>> >>>>> >>>>> >>>>> Claus Ibsen-2 wrote: >>>>>> >>>>>> Hi >>>>>> >>>>>> Have you read the warning on top of the JMS wiki page? >>>>>> http://camel.apache.org/jms.html >>>>>> >>>>>> >>>>>> On Fri, Nov 27, 2009 at 11:10 AM, titexe <tit...@yahoo.fr> wrote: >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I am analyzing a problem of memory leak, >>>>>>> >>>>>>> each execution for flow camel, memory increases, but there's not >>>>>>> releasing >>>>>>> memory after. >>>>>>> >>>>>>> analyzing the problem with jconsole and jvisualvm, there's a lot of >>>>>>> threads >>>>>>> (ActiveMQ Session ID: Server-1997-XXXXXXXXXX) which is still in wait >>>>>>> and >>>>>>> will not release, these threads are added more and more each time you >>>>>>> run >>>>>>> flow camel: >>>>>>> >>>>>>> Name of threads : ActiveMQ Session ID: Server-1997-XXXXXXXXXX >>>>>>> >>>>>>> Is not that there's a way to release those threads or configuration >>>>>>> to >>>>>>> do? >>>>>>> >>>>>>> VersionJava: 1.6 >>>>>>> Fuse Message Broker Version: V5.3.0.3 >>>>>>> Camel Version: 1.6.1.2 >>>>>>> >>>>>>> >>>>>>> Thank you in advance >>>>>>> >>>>>>> Best regards. >>>>>>> >>>>>>> titexe >>>>>>> -- >>>>>>> View this message in context: >>>>>>> http://old.nabble.com/Camel%3A-memory-management-%28memory-leak%29-tp26540277p26540277.html >>>>>>> Sent from the Camel - Users mailing list archive at Nabble.com. >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Claus Ibsen >>>>>> Apache Camel Committer >>>>>> >>>>>> Author of Camel in Action: http://www.manning.com/ibsen/ >>>>>> Open Source Integration: http://fusesource.com >>>>>> Blog: http://davsclaus.blogspot.com/ >>>>>> Twitter: http://twitter.com/davsclaus >>>>>> >>>>>> >>>>> >>>>> -- >>>>> View this message in context: >>>>> http://old.nabble.com/Camel%3A-memory-management-%28memory-leak%29-tp26540277p26540657.html >>>>> Sent from the Camel - Users mailing list archive at Nabble.com. >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Claus Ibsen >>>> Apache Camel Committer >>>> >>>> Author of Camel in Action: http://www.manning.com/ibsen/ >>>> Open Source Integration: http://fusesource.com >>>> Blog: http://davsclaus.blogspot.com/ >>>> Twitter: http://twitter.com/davsclaus >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://old.nabble.com/Camel%3A-memory-management-%28memory-leak%29-tp26540277p26540897.html >>> Sent from the Camel - Users mailing list archive at Nabble.com. >>> >>> >> >> >> >> -- >> Claus Ibsen >> Apache Camel Committer >> >> Author of Camel in Action: http://www.manning.com/ibsen/ >> Open Source Integration: http://fusesource.com >> Blog: http://davsclaus.blogspot.com/ >> Twitter: http://twitter.com/davsclaus >> >> > > -- > View this message in context: > http://old.nabble.com/Camel%3A-memory-management-%28memory-leak%29-tp26540277p26542792.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
