Camel.trunk.notest - Build # 2119 - Still Failing

2014-07-24 Thread Apache Jenkins Server
The Apache Jenkins build system has built Camel.trunk.notest (build #2119) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.trunk.notest/2119/ to view the results.

[GitHub] camel pull request: CAMEL-7632: Add streaming mode to camel-splunk...

2014-07-24 Thread dmitrimedvedev
GitHub user dmitrimedvedev opened a pull request: https://github.com/apache/camel/pull/226 CAMEL-7632: Add streaming mode to camel-splunk consumer You can merge this pull request into a Git repository by running: $ git pull https://github.com/dmitrimedvedev/camel master Alter

Re: Memory leak with Message History

2014-07-24 Thread David Karlsen
Nope - images not appearing. 2014-07-24 16:00 GMT+02:00 Claus Ibsen : > Hi > > Anyone able to see those images? Maybe you can log a JIRA and attach the > images there. Not sure if this mailing list accepts images and embedded > files in mails etc. > > > > > On Thu, Jul 24, 2014 at 3:42 PM, Raul

Re: Memory leak with Message History

2014-07-24 Thread Raul Kripalani
My bad. They don't even show up in Nabble :( Probably because I copy-pasted rather than attaching. You got it: https://issues.apache.org/jira/browse/CAMEL-7635 Let's continue the discussion in the ticket. If you need more info about the dump or want me to run additional OQL queries, feel free to

Re: Memory leak with Message History

2014-07-24 Thread Claus Ibsen
Hi Anyone able to see those images? Maybe you can log a JIRA and attach the images there. Not sure if this mailing list accepts images and embedded files in mails etc. On Thu, Jul 24, 2014 at 3:42 PM, Raul Kripalani wrote: > Team, > > We just had an OOM incident in our dev environments after

Memory leak with Message History

2014-07-24 Thread Raul Kripalani
Team, We just had an OOM incident in our dev environments after upgrading from Camel 2.10.3 to 2.13.1. Heap settings have remained untouched. A heap dump showed millions of DefaultMessageHistory instances retained (see screenshot), along with their corresponding Date and StopWatch instances. Obvi