camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-3906) Consumer and Producer names in JMX
Date Tue, 10 May 2011 06:48:04 GMT


Claus Ibsen commented on CAMEL-3906:

Well you could add consumers/processors etc that are not part of a route. Just use the Camel
API for that. And if you have enabled JMX to enlist always then it will do that. But I guess
its uncommon and not something that the regular Camel end users does.

And yes the endpoint being part of the MBean key would be an issue if the endpoint is dynamic
updated afterwards.
We could of course notice this in the documentation that the MBean key is the starting endpoint
uri. And the actual uri is the attribute. So in case people dynamic change it they are aware
of this fact. I think thats sufficient. Also I guess it would be uncommon/rare to adjust this.

> Consumer and Producer names in JMX
> ----------------------------------
>                 Key: CAMEL-3906
>                 URL:
>             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
> [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:

View raw message