You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "William Tam (JIRA)" <ji...@apache.org> on 2008/07/07 07:07:00 UTC

[jira] Created: (CAMEL-679) Instrumentation agent should be able to register multiple instances of a processor

Instrumentation agent should be able to register multiple instances of a processor
----------------------------------------------------------------------------------

                 Key: CAMEL-679
                 URL: https://issues.apache.org/activemq/browse/CAMEL-679
             Project: Apache Camel
          Issue Type: Bug
          Components: camel-core
            Reporter: William Tam
            Priority: Minor
             Fix For: 1.4.0


If you have a route like this: from("jms:queue").to("bean:testBean").to("bean:testBean"),
the second instance of the processor "to(bean:testBean)" will fail to register with mbean server because of duplicated objectname.  As a result, only one instance of the "to(bean:testBean)" processor is visible to mbean server and we won't set the performance counter of the second instance.

 http://www.nabble.com/Starting-Camel-context-causes-JMX-exception.-tp18304692s22882p18304692.html


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


[jira] Updated: (CAMEL-679) Instrumentation agent should be able to register multiple instances of a processor

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

William Tam updated CAMEL-679:
------------------------------

    Attachment: patch.txt

Patch to include node id in processor's objectname.  Since node id is an option id, instrumentation agent adds instance id into the objectname as well.

> Instrumentation agent should be able to register multiple instances of a processor
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-679
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-679
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: William Tam
>            Priority: Minor
>             Fix For: 1.4.0
>
>         Attachments: patch.txt
>
>
> If you have a route like this: from("jms:queue").to("bean:testBean").to("bean:testBean"),
> the second instance of the processor "to(bean:testBean)" will fail to register with mbean server because of duplicated objectname.  As a result, only one instance of the "to(bean:testBean)" processor is visible to mbean server and we won't set the performance counter of the second instance.
>  http://www.nabble.com/Starting-Camel-context-causes-JMX-exception.-tp18304692s22882p18304692.html

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


[jira] Resolved: (CAMEL-679) Instrumentation agent should be able to register multiple instances of a processor

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

Claus Ibsen resolved CAMEL-679.
-------------------------------

    Resolution: Fixed

Applied patch with thanks to William Tam.

> Instrumentation agent should be able to register multiple instances of a processor
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-679
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-679
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: William Tam
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>         Attachments: patch.txt
>
>
> If you have a route like this: from("jms:queue").to("bean:testBean").to("bean:testBean"),
> the second instance of the processor "to(bean:testBean)" will fail to register with mbean server because of duplicated objectname.  As a result, only one instance of the "to(bean:testBean)" processor is visible to mbean server and we won't set the performance counter of the second instance.
>  http://www.nabble.com/Starting-Camel-context-causes-JMX-exception.-tp18304692s22882p18304692.html

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


[jira] Updated: (CAMEL-679) Instrumentation agent should be able to register multiple instances of a processor

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

William Tam updated CAMEL-679:
------------------------------

    Attachment: patch.txt

> Instrumentation agent should be able to register multiple instances of a processor
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-679
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-679
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: William Tam
>            Priority: Minor
>             Fix For: 1.4.0
>
>         Attachments: patch.txt
>
>
> If you have a route like this: from("jms:queue").to("bean:testBean").to("bean:testBean"),
> the second instance of the processor "to(bean:testBean)" will fail to register with mbean server because of duplicated objectname.  As a result, only one instance of the "to(bean:testBean)" processor is visible to mbean server and we won't set the performance counter of the second instance.
>  http://www.nabble.com/Starting-Camel-context-causes-JMX-exception.-tp18304692s22882p18304692.html

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


[jira] Updated: (CAMEL-679) Instrumentation agent should be able to register multiple instances of a processor

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

William Tam updated CAMEL-679:
------------------------------

    Attachment:     (was: patch.txt)

> Instrumentation agent should be able to register multiple instances of a processor
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-679
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-679
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: William Tam
>            Priority: Minor
>             Fix For: 1.4.0
>
>         Attachments: patch.txt
>
>
> If you have a route like this: from("jms:queue").to("bean:testBean").to("bean:testBean"),
> the second instance of the processor "to(bean:testBean)" will fail to register with mbean server because of duplicated objectname.  As a result, only one instance of the "to(bean:testBean)" processor is visible to mbean server and we won't set the performance counter of the second instance.
>  http://www.nabble.com/Starting-Camel-context-causes-JMX-exception.-tp18304692s22882p18304692.html

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


[jira] Assigned: (CAMEL-679) Instrumentation agent should be able to register multiple instances of a processor

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

Claus Ibsen reassigned CAMEL-679:
---------------------------------

    Assignee: Claus Ibsen

> Instrumentation agent should be able to register multiple instances of a processor
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-679
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-679
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: William Tam
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>         Attachments: patch.txt
>
>
> If you have a route like this: from("jms:queue").to("bean:testBean").to("bean:testBean"),
> the second instance of the processor "to(bean:testBean)" will fail to register with mbean server because of duplicated objectname.  As a result, only one instance of the "to(bean:testBean)" processor is visible to mbean server and we won't set the performance counter of the second instance.
>  http://www.nabble.com/Starting-Camel-context-causes-JMX-exception.-tp18304692s22882p18304692.html

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


[jira] Closed: (CAMEL-679) Instrumentation agent should be able to register multiple instances of a processor

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

William Tam closed CAMEL-679.
-----------------------------


> Instrumentation agent should be able to register multiple instances of a processor
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-679
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-679
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: William Tam
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>         Attachments: patch.txt
>
>
> If you have a route like this: from("jms:queue").to("bean:testBean").to("bean:testBean"),
> the second instance of the processor "to(bean:testBean)" will fail to register with mbean server because of duplicated objectname.  As a result, only one instance of the "to(bean:testBean)" processor is visible to mbean server and we won't set the performance counter of the second instance.
>  http://www.nabble.com/Starting-Camel-context-causes-JMX-exception.-tp18304692s22882p18304692.html

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


[jira] Updated: (CAMEL-679) Instrumentation agent should be able to register multiple instances of a processor

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

Claus Ibsen updated CAMEL-679:
------------------------------

    Affects Version/s: 1.4.0

> Instrumentation agent should be able to register multiple instances of a processor
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-679
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-679
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: William Tam
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>         Attachments: patch.txt
>
>
> If you have a route like this: from("jms:queue").to("bean:testBean").to("bean:testBean"),
> the second instance of the processor "to(bean:testBean)" will fail to register with mbean server because of duplicated objectname.  As a result, only one instance of the "to(bean:testBean)" processor is visible to mbean server and we won't set the performance counter of the second instance.
>  http://www.nabble.com/Starting-Camel-context-causes-JMX-exception.-tp18304692s22882p18304692.html

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