Hi No not really as the JVM is a single process on the OS level and so many of the tooling for process level memory monitoring is based on the entire JVM.
If you have a doubt that a particular route is taking up more memory, you could try to isolate it and run it it alone in a JVM then you have all the memory monitoring tooling available. For the JVM you could take a heap-dump and analyse it and see for example if there are large object trees or such things that take up a considerable amount of memory. With this information you can possible pin-point that to a Camel route / component / custom bean / processor or what else. You can also stop/suspend the other routes, and then keep 1 route running and then monitor the JVM for object allocations and whatnot and see if the route allocations too much objects / takes up too much memory. On Thu, Mar 29, 2018 at 2:29 AM, Weiqiang Wang <weiqi...@uber.com> wrote: > Hi, > > Is there a way to monitor memory usage for each individual route at runtime. > > Thank you > > -- > Weiqiang -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
