Hi Paul Thanks for coming back and letting us know you have it resolved now and sharing the solutions to the problem.
On Thu, Feb 25, 2010 at 11:19 AM, Paul Phillips <[email protected]> wrote: > > I was using camel 2.1 > > Have upgraded to 2.2 now > > I have since discovered that the "extra" jdbc producers were my own fault > anyway because of a classic mistake. > > During my route a was creating a new ProducerTemplate in a processor. > > This meant that it had its own ProducerCache that was empty thus making it > register a new jdbc producer with jmx. > > There was also another unrelated problem with my app. I use an embedded hsql > database and the default for tables is to create them as "memory" tables. > This means the whole of my 200meg log table was being loaded into the jvm! > > Once I sorted these 2 issues the memory usage is looking a hell of a lot > better.... > > Thanks for your time anyway! > > Paul. > -- > View this message in context: > http://old.nabble.com/jdbc-producers-tp27669119p27714388.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
