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 2008/07/17 10:42:00 UTC

[jira] Created: (CAMEL-732) JMX Instrumentation - check for already registered before registering

JMX Instrumentation - check for already registered before registering
---------------------------------------------------------------------

                 Key: CAMEL-732
                 URL: https://issues.apache.org/activemq/browse/CAMEL-732
             Project: Apache Camel
          Issue Type: Improvement
          Components: camel-core
    Affects Versions: 1.4.0
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
            Priority: Minor
             Fix For: 1.4.0


Camel does not check for already registered mbeans. There can be shared endpoints in the camel routes etc.

We used to have an instance count and everything but at the end a jms endpoint such as "activemq:topic:orders" can be reused in several routes and we should in fact only register it once.

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


[jira] Commented: (CAMEL-732) JMX Instrumentation - check for already registered before registering

Posted by "Charles Moulliard (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44357#action_44357 ] 

Charles Moulliard commented on CAMEL-732:
-----------------------------------------

Claus,

I have tested and the error message does not appear anymore. You can close the issue.

Many thanks


> JMX Instrumentation - check for already registered before registering
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-732
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-732
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> Camel does not check for already registered mbeans. There can be shared endpoints in the camel routes etc.
> We used to have an instance count and everything but at the end a jms endpoint such as "activemq:topic:orders" can be reused in several routes and we should in fact only register it once.

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


[jira] Resolved: (CAMEL-732) JMX Instrumentation - check for already registered before registering

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-732.
-------------------------------

    Resolution: Fixed

Charles. Thanks a lot for reporting and testing the fixes. We appreciate all you patient work with us and the Camel.

> JMX Instrumentation - check for already registered before registering
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-732
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-732
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> Camel does not check for already registered mbeans. There can be shared endpoints in the camel routes etc.
> We used to have an instance count and everything but at the end a jms endpoint such as "activemq:topic:orders" can be reused in several routes and we should in fact only register it once.

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


[jira] Commented: (CAMEL-732) JMX Instrumentation - check for already registered before registering

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44353#action_44353 ] 

Claus Ibsen commented on CAMEL-732:
-----------------------------------

Fix commited to SVN:
http://svn.apache.org/viewvc?view=rev&revision=677549

> JMX Instrumentation - check for already registered before registering
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-732
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-732
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> Camel does not check for already registered mbeans. There can be shared endpoints in the camel routes etc.
> We used to have an instance count and everything but at the end a jms endpoint such as "activemq:topic:orders" can be reused in several routes and we should in fact only register it once.

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


[jira] Commented: (CAMEL-732) JMX Instrumentation - check for already registered before registering

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44352#action_44352 ] 

Claus Ibsen commented on CAMEL-732:
-----------------------------------

See nabble:
http://www.nabble.com/How-can-avoid-to-have-such-error-message-%22instanceAllreadyExistsException%22---td18503700s22882.html

> JMX Instrumentation - check for already registered before registering
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-732
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-732
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> Camel does not check for already registered mbeans. There can be shared endpoints in the camel routes etc.
> We used to have an instance count and everything but at the end a jms endpoint such as "activemq:topic:orders" can be reused in several routes and we should in fact only register it once.

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


[jira] Work started: (CAMEL-732) JMX Instrumentation - check for already registered before registering

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on CAMEL-732 started by Claus Ibsen.

> JMX Instrumentation - check for already registered before registering
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-732
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-732
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> Camel does not check for already registered mbeans. There can be shared endpoints in the camel routes etc.
> We used to have an instance count and everything but at the end a jms endpoint such as "activemq:topic:orders" can be reused in several routes and we should in fact only register it once.

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