camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-735) JMX Instrumentation - shared endpoints
Date Thu, 14 May 2009 14:05:50 GMT

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

Hadrian Zbarcea commented on CAMEL-735:
---------------------------------------

The 1.6.1 release is already built.  If the community vote passes this will have to wait for
1.6.2.

> JMX Instrumentation - shared endpoints
> --------------------------------------
>
>                 Key: CAMEL-735
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-735
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>             Fix For: 2.0-M1
>
>
> We should be sure that when registering the mbean the objectname is really the correct
one we use. If its a shared endpoint then we should only have a single instance. If not then
we should of course have multi.
> And beware the *WebSphere* 6.1 can have issues with the objectname as it prefixes the
objectname with its own server context (the /cell/node stuff). 
> We should alvoid confusing end-users with "InstanceAlreadyRegistered" exceptions with
stacktraces, they should not be logged if it's not really a problem.
> William Tam has a good grip on this, so we will work together with him to improve it.
> See nabble:
> http://www.nabble.com/How-can-avoid-to-have-such-error-message-%22instanceAllreadyExistsException%22---td18503700s22882.html

-- 
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