Camel route using "mock:" endpoints uses a lot of JVM heap
Issue
A Camel application uses mock: endpoints for testing:
...
from("direct:testdata")
.to("mock:test_endpoint");
It is observed that, under load, a large and increasing amount of JVM heap is used. Inspection of the heap reveals large numbers of org.apache.camel.component.mock.MockEndpoint.XXX instances.
Environment
- Red Hat JBoss Fuse
- 6.x
- Camel 2.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
