[
https://issues.apache.org/activemq/browse/CAMEL-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-2975:
-------------------------------
Comment: was deleted
(was: You should be able to specify a route to not be enlisted in JMX.
{code}
from("xxx").disableJMX().to("yyy");
{code}
And in XML
{code:xml}
<route disableJMX="true">
<from uri="xxx"/>
<to uri="yyy"/>
</route>
{code}
The trick is the current API in Camel enlists in JMX by default if its enabled.
It could take a bit of refactoring to have it being able know that the route is
not enlisted. For example the consumers/endpoints/services which is created by
that particular route should also *not* be enlisted in JMX. And hence they need
to be able to understand this, by asking their parent route if JMX is disabled
or not.
)
> Shutting down a route should dispose JMX mbeans for that particular route
> -------------------------------------------------------------------------
>
> Key: CAMEL-2975
> URL: https://issues.apache.org/activemq/browse/CAMEL-2975
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.4.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.5.0
>
>
> If Camel end uses add temporary routes on the fly, and then want those temp
> routes to be deleted, they need to shutdown the route.
> And we should then unregister the associated JMX mbeans that the route solely
> uses. This can be a bit tricky to do as the current architecture will
> unregister mbeans on camel shutdown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
