camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-3135) Option on route to specify that JMX should be disabled
Date Sun, 19 Sep 2010 09:32:40 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61908#action_61908
] 

Claus Ibsen commented on CAMEL-3135:
------------------------------------

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}a
<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.


> Option on route to specify that JMX should be disabled
> ------------------------------------------------------
>
>                 Key: CAMEL-3135
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3135
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: Future
>
>
> For example if you create temporary routes which are short lived and you don't want those
enlisted for management.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message