Hi You can contact commercial vendors whom have prioritized help for their customers. For community help, its often harder to help with production issues.
I suggest to build as small sample application that reproduces this and put on github or as a .zip file for others to reproduce. And for inflight exchanges it can also be that remote systems do not respond, or a timeout is not triggering the removal, or something but its hard to tell without code. And btw if you use CXF then try with synchronous=true as it had an issue in the past with this (but thats been a while). On Thu, Apr 30, 2020 at 9:30 AM Sadiya Kazi <kazisadiya...@gmail.com> wrote: > > Currently we are facing an issue with memory leak in JVM. The application > uses Apache camel as an integration tool. Since the latest release, it > observed that the application works on server for three days and stops with > OutOfMemory Error on the fourth day. The heap dump states that the memory > is loaded with Camel InflightRepository objects which gradually increases > and ends up eating all the memory. There is no change in camel version as > well in latest release. After searching related topics on, I found that > exchange gets added in Camel Inflight Repository but are not removed as > ExchangeId get manipulated but no where in the code we are setting the > exchangeId of the route. Can any one of you please help me getting rid of > this memory leak issue? -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
