You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org> on 2010/07/14 13:04:50 UTC

[jira] Created: (SYNAPSE-669) Improve JMX Monitoring Capabilities of the NHTTP Transport

Improve JMX Monitoring Capabilities of the NHTTP Transport
----------------------------------------------------------

                 Key: SYNAPSE-669
                 URL: https://issues.apache.org/jira/browse/SYNAPSE-669
             Project: Synapse
          Issue Type: Improvement
          Components: Transports
    Affects Versions: NIGHTLY
            Reporter: Hiranya Jayathilaka
            Assignee: Hiranya Jayathilaka
             Fix For: 2.0


The existing JMX monitoring capabilities of the NHTTP transport are very basic and minimal. While they are "good enough", they are not at all sufficient for a large scale enterprise service bus deployment. I have been working on improving the JMX monitoring support of the NHTTP transport recently and I would like to contribute these features to the Synapse main development trunk. Basically we'll have three new MBeans to monitor the transport:

1. LatencyView - Monitors the latency incurred by Synapse when mediating messages back and forth using the NHTTP transport
2. ThreadingView - Monitors transport thread pools
3. ConnectionsView - Monitors the usage of HTTP connections by the transport listener and sender

I will take an incremental approach, as much as possible, when checking these features into the trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


[jira] Resolved: (SYNAPSE-669) Improve JMX Monitoring Capabilities of the NHTTP Transport

Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SYNAPSE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiranya Jayathilaka resolved SYNAPSE-669.
-----------------------------------------

    Resolution: Fixed

Proposed improvements are checked into the trunk

> Improve JMX Monitoring Capabilities of the NHTTP Transport
> ----------------------------------------------------------
>
>                 Key: SYNAPSE-669
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-669
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: NIGHTLY
>            Reporter: Hiranya Jayathilaka
>            Assignee: Hiranya Jayathilaka
>             Fix For: 2.0
>
>         Attachments: connections-view.png, latency-view.png, threading-view.png
>
>
> The existing JMX monitoring capabilities of the NHTTP transport are very basic and minimal. While they are "good enough", they are not at all sufficient for a large scale enterprise service bus deployment. I have been working on improving the JMX monitoring support of the NHTTP transport recently and I would like to contribute these features to the Synapse main development trunk. Basically we'll have three new MBeans to monitor the transport:
> 1. LatencyView - Monitors the latency incurred by Synapse when mediating messages back and forth using the NHTTP transport
> 2. ThreadingView - Monitors transport thread pools
> 3. ConnectionsView - Monitors the usage of HTTP connections by the transport listener and sender
> I will take an incremental approach, as much as possible, when checking these features into the trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


[jira] Updated: (SYNAPSE-669) Improve JMX Monitoring Capabilities of the NHTTP Transport

Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SYNAPSE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiranya Jayathilaka updated SYNAPSE-669:
----------------------------------------

    Attachment: threading-view.png
                latency-view.png
                connections-view.png

Screenshots of the three new MBeans as displayed by JConsole 

> Improve JMX Monitoring Capabilities of the NHTTP Transport
> ----------------------------------------------------------
>
>                 Key: SYNAPSE-669
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-669
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: NIGHTLY
>            Reporter: Hiranya Jayathilaka
>            Assignee: Hiranya Jayathilaka
>             Fix For: 2.0
>
>         Attachments: connections-view.png, latency-view.png, threading-view.png
>
>
> The existing JMX monitoring capabilities of the NHTTP transport are very basic and minimal. While they are "good enough", they are not at all sufficient for a large scale enterprise service bus deployment. I have been working on improving the JMX monitoring support of the NHTTP transport recently and I would like to contribute these features to the Synapse main development trunk. Basically we'll have three new MBeans to monitor the transport:
> 1. LatencyView - Monitors the latency incurred by Synapse when mediating messages back and forth using the NHTTP transport
> 2. ThreadingView - Monitors transport thread pools
> 3. ConnectionsView - Monitors the usage of HTTP connections by the transport listener and sender
> I will take an incremental approach, as much as possible, when checking these features into the trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


[jira] Commented: (SYNAPSE-669) Improve JMX Monitoring Capabilities of the NHTTP Transport

Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SYNAPSE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889778#action_12889778 ] 

Hiranya Jayathilaka commented on SYNAPSE-669:
---------------------------------------------

The threading view is now implemented in the trunk. This implementation is based on a generic JMX MBean which is available in the synapse-commons module.

> Improve JMX Monitoring Capabilities of the NHTTP Transport
> ----------------------------------------------------------
>
>                 Key: SYNAPSE-669
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-669
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: NIGHTLY
>            Reporter: Hiranya Jayathilaka
>            Assignee: Hiranya Jayathilaka
>             Fix For: 2.0
>
>
> The existing JMX monitoring capabilities of the NHTTP transport are very basic and minimal. While they are "good enough", they are not at all sufficient for a large scale enterprise service bus deployment. I have been working on improving the JMX monitoring support of the NHTTP transport recently and I would like to contribute these features to the Synapse main development trunk. Basically we'll have three new MBeans to monitor the transport:
> 1. LatencyView - Monitors the latency incurred by Synapse when mediating messages back and forth using the NHTTP transport
> 2. ThreadingView - Monitors transport thread pools
> 3. ConnectionsView - Monitors the usage of HTTP connections by the transport listener and sender
> I will take an incremental approach, as much as possible, when checking these features into the trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


[jira] Commented: (SYNAPSE-669) Improve JMX Monitoring Capabilities of the NHTTP Transport

Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SYNAPSE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889073#action_12889073 ] 

Hiranya Jayathilaka commented on SYNAPSE-669:
---------------------------------------------

The latency view is now implemented in the trunk (r964719)

> Improve JMX Monitoring Capabilities of the NHTTP Transport
> ----------------------------------------------------------
>
>                 Key: SYNAPSE-669
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-669
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: NIGHTLY
>            Reporter: Hiranya Jayathilaka
>            Assignee: Hiranya Jayathilaka
>             Fix For: 2.0
>
>
> The existing JMX monitoring capabilities of the NHTTP transport are very basic and minimal. While they are "good enough", they are not at all sufficient for a large scale enterprise service bus deployment. I have been working on improving the JMX monitoring support of the NHTTP transport recently and I would like to contribute these features to the Synapse main development trunk. Basically we'll have three new MBeans to monitor the transport:
> 1. LatencyView - Monitors the latency incurred by Synapse when mediating messages back and forth using the NHTTP transport
> 2. ThreadingView - Monitors transport thread pools
> 3. ConnectionsView - Monitors the usage of HTTP connections by the transport listener and sender
> I will take an incremental approach, as much as possible, when checking these features into the trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


[jira] Commented: (SYNAPSE-669) Improve JMX Monitoring Capabilities of the NHTTP Transport

Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SYNAPSE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889797#action_12889797 ] 

Hiranya Jayathilaka commented on SYNAPSE-669:
---------------------------------------------

The proposed three new MBeans have been implemented in the trunk. I will soon attach some screenshots for the reference.

> Improve JMX Monitoring Capabilities of the NHTTP Transport
> ----------------------------------------------------------
>
>                 Key: SYNAPSE-669
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-669
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: NIGHTLY
>            Reporter: Hiranya Jayathilaka
>            Assignee: Hiranya Jayathilaka
>             Fix For: 2.0
>
>         Attachments: connections-view.png, latency-view.png, threading-view.png
>
>
> The existing JMX monitoring capabilities of the NHTTP transport are very basic and minimal. While they are "good enough", they are not at all sufficient for a large scale enterprise service bus deployment. I have been working on improving the JMX monitoring support of the NHTTP transport recently and I would like to contribute these features to the Synapse main development trunk. Basically we'll have three new MBeans to monitor the transport:
> 1. LatencyView - Monitors the latency incurred by Synapse when mediating messages back and forth using the NHTTP transport
> 2. ThreadingView - Monitors transport thread pools
> 3. ConnectionsView - Monitors the usage of HTTP connections by the transport listener and sender
> I will take an incremental approach, as much as possible, when checking these features into the trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org