[
https://issues.apache.org/activemq/browse/CAMEL-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46378#action_46378
]
Claus Ibsen commented on CAMEL-865:
-----------------------------------
Looks much better.
Shouldn't we also have a {{producers}} folder?
Currently they are listed with processeros:
- bean1
- to1
- to2
As we don't have producers we can not invoke start/stop JMX operations.
And the {{routes}} we have is basically all the consumers listed again. How
should we structure routes? As James write it's hard to have a nested folder
structure to represent the complex route paths you can do in the DSL. Currently
routes is listed as:
- node1
- node2
- node3
See new attached screenshot
> 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
> Priority: Blocker
> Fix For: 1.5.0
>
> Attachments: camelJmx.png, claus-jms-screenshot.jpg
>
>
> 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.
