The attached test case simulates a condition that I believe is causing a memory leak, leading to an eventual OutOfMemory error. Just apply the patch to camel-core and do "mvn clean compile test -Dtest=AggregatorExceptionTest" to run the test. After a minute or so the test will fail, the patch updates the pom so that -XX:+HeapDumpOnOutOfMemoryError is passed to the JVM, so you'll have a heap dump created in the current working directory. You can use this tool to analyze the heap. Just click on the "Leak suspects" link, you'll see that the bulk of the heap is taken up by InstrumentationProcessor, drilling into the object hierarchy you'll see that there's an element of the LinkedList in BatchSender that's 98% of the heap. Will post a screenshot also.