[
https://issues.apache.org/activemq/browse/CAMEL-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45197#action_45197
]
James Strachan commented on CAMEL-865:
--------------------------------------
btw am thinking mangling the URIs into deeply nested trees is not that helpful
for JMX tools and command line tools etc.
Just having 1 folder depth seems better - maybe we just generate unique IDs for
each node (endpoint/route) and use that as the name within the Endpoints /
Routes folder.
For routes we can use RouteType.idOrCreate() to get a unique ID per camel
context
> mbeans don't seem to be correct - looking in JConsole at routes, don't seem
> to see 1 mbean per route and 1 mbean per endpoint
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-865
> URL: https://issues.apache.org/activemq/browse/CAMEL-865
> Project: Apache Camel
> Issue Type: Improvement
> Components: jmx
> Reporter: James Strachan
> Assignee: Hadrian Zbarcea
> Fix For: 1.5.0
>
> Attachments: camelJmx.png
>
>
> we should really have folders within each camelcontext like this...
> {code}
> camelContext-something/
> endpoints/
> endpoint-x
> endpoint-y
> routes/
> route-a
> route-b
> consumers/
> consumer-1234
> {code}
> i.e. we should be able to find all the endpoints in JMX easily looking in a
> single JMX 'folder' ditto for routes
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
