[
https://issues.apache.org/jira/browse/CAMEL-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030913#comment-13030913
]
Ben O'Day commented on CAMEL-3906:
----------------------------------
For the consumer name, agreed that the endpoint name and trimmed URI would
help. Also, I removed the identity hash code because I thought only a single
consumer could exist for a given endpointURI...perhaps not.
For the processors being altered after startup, I see your point. But, it
seems like it would be an issue regardless of whether we name the MBean using
the endpointURI or construct an MBean path based on endpointURIs. Can we
easily re-register with JMX when these types of changes occur?
> Consumer and Producer names in JMX
> ----------------------------------
>
> Key: CAMEL-3906
> URL: https://issues.apache.org/jira/browse/CAMEL-3906
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Mitko Kolev
> Assignee: Ben O'Day
> Priority: Minor
> Fix For: 2.8.0
>
> Attachments: CAMEL-3906.patch
>
>
> Currently the consumer and producer names in JMX have a name based on their
> java instance [1]. Due to this it is not obvious what is the endpoint of the
> consumers/producers.
> It can be improved to use name in the JMX tree based on endpoint URI of the
> consumer/producer endpoints (combined with identityHashcode) to help in the
> overview to faster spot the desired consumer.
> [1] Copy/paste from the DefaultManagementNamingStrategy
> ...
> String name = consumer.getClass().getSimpleName();
> if (ObjectHelper.isEmpty(name)) {
> name = "Consumer";
> }
> buffer.append(KEY_NAME + "=")
> .append(name)
>
> .append("(").append(ObjectHelper.getIdentityHashCode(consumer)).append(")");
> ...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
