You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/09/19 11:30:42 UTC
[jira] Created: (CAMEL-3135) Option on route to specify that JMX
should be disabled
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.
[jira] Issue Comment Edited: (CAMEL-3135) Option on route to
specify that JMX should be disabled
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61908#action_61908 ]
Claus Ibsen edited comment on CAMEL-3135 at 9/19/10 5:31 AM:
-------------------------------------------------------------
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.
was (Author: davsclaus):
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.
[jira] Commented: (CAMEL-3135) Option on route to specify that JMX
should be disabled
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CAMEL-3135) Option on route to specify that JMX
should be disabled
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-3135:
-------------------------------
Fix Version/s: (was: Future)
3.0.0
> 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: 3.0.0
>
>
> 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.