[jira] Created: (CAMEL-865) 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

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (CAMEL-865) 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

JIRA jira@apache.org
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


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 | Threaded
Open this post in threaded view
|

[jira] Updated: (CAMEL-865) 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

JIRA jira@apache.org

     [ 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 | Threaded
Open this post in threaded view
|

[jira] Commented: (CAMEL-865) 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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (CAMEL-865) 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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

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

    Priority: Blocker  (was: Major)

> 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
>
>
> 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 | Threaded
Open this post in threaded view
|

[jira] Work started: (CAMEL-865) 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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Work on CAMEL-865 started by Hadrian Zbarcea.

> 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: 2.0.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 | Threaded
Open this post in threaded view
|

[jira] Updated: (CAMEL-865) 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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Hadrian Zbarcea updated CAMEL-865:
----------------------------------

    Fix Version/s: 1.5.0
                       (was: 2.0.0)

> 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
>
>
> 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 | Threaded
Open this post in threaded view
|

[jira] Commented: (CAMEL-865) 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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/activemq/browse/CAMEL-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46266#action_46266 ]

Hadrian Zbarcea commented on CAMEL-865:
---------------------------------------

Fix committed.  Awaiting documentation updates.

> 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
>
>
> 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 | Threaded
Open this post in threaded view
|

[jira] Commented: (CAMEL-865) 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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (CAMEL-865) 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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Claus Ibsen updated CAMEL-865:
------------------------------

    Attachment: claus-jms-screenshot.jpg

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

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (CAMEL-865) 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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Hadrian Zbarcea updated CAMEL-865:
----------------------------------

    Priority: Major  (was: Blocker)

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

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (CAMEL-865) 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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Hadrian Zbarcea resolved CAMEL-865.
-----------------------------------

    Resolution: Fixed

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