I've created https://issues.apache.org/jira/browse/CAMEL-5435 CAMEL-5435
for the issue.
--
View this message in context:
http://camel.465427.n5.nabble.com/Suspending-resuming-routes-via-a-policy-not-reflected-in-JMX-tp5715701p5715823.html
Sent from the Camel - Users mailing list archive at Nabb
We're using Camel 2.9.2.
I'm using the 'state' attribute and the 'getState()' operation on the route
list under routes for the org.apache.camel mbean via JConsole.
If I'm using JMX via Java I can query for all routes using '.. = new
ObjectName("org.apache.camel:type=routes,*")' and then check the
I've created a RoutePolicy which extends RoutePolicySupport for throttling
some routes. I've noticed that when routes are suspended or resumed by
RoutePolicySupport.startConsumer and RoutePolicySupport.stopConsumer the
status is incorrect when I look it up using JMX. I.e. if I call
RoutePolicySuppo
Thanks, I've upgraded to Camel 2.9.2 and that seems to have resolved the
memory leak.
It seems that there were FileConsumer objects being held onto in the
threadpool with a few being created (and not released) every few minutes.
--
View this message in context:
http://camel.465427.n5.nabble.com/
I've been looking into a memory leak we're experiencing with our Camel
application and have found that the culprit seems to be
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.
Using MAT & taking heap dumps at the start and end of an 8 day period I can
see that the memory consumption for Defau
Just wondering if there's any update on this?
We have a similar requirement with our gateway application. We currently use
the Came SMPP component to act as a SMPP client and send/receive messages
with SMSCs; but we now have a potential requirement to build a SMPP
interface for our users. So in es
