[ https://issues.apache.org/activemq/browse/CAMEL-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Bentley reopened CAMEL-735: -------------------------------- We can not use Milestone builds on our project :-( Can you please port this fix to the 1.6.1. branch > 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.