[ 
https://issues.apache.org/activemq/browse/CAMEL-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Strachan updated CAMEL-865:
---------------------------------

    Attachment: camelJmx.png

here's a screen shot of running 

{code}
cd examples/camel-example-spring
mvn camel:run
{code}

then looking in jconsole.

The routes and endpoints should look like this

{code}
from("file:src/data?noop=true").
                to("jms:test.MyQueue");

        from("jms:test.MyQueue").
                to("file://target/test?noop=true");

        // set up a listener on the file component
        from("file://target/test?noop=true").
                bean(new SomeBean());
{code}

but for some reason the JMS endpoints don't appear and the routes are a bit 
cryptic.

> 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.

Reply via email to