You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Aki Yoshida <el...@googlemail.com> on 2011/08/24 13:30:30 UTC
JMX instrumentation for WS-RM checked in
Hi,
I checked in an implementation of JMX instrumentation for the WS-RM
components in trunk.
In short, RMManager and RMEndpoint objects have their instrumentation
beans and various inspection methods into the internal states of the
runtime artifacts such as RM source and destination sequences, the
status of the message retransmission are exposed over these beans.
To get an idea, you can simply activate JMX for your bus configuraiton
and use jconsole to connect to the server. If your bus activates the
reliable messaging feature, you will see the managed RMManger entry.
The corresponding RMEndpoint entry will be registered when the
endpoint is used.
Most instrumentation methods are accessible from this managed
RMEndpoint instance. For example, you can display the current state of
a given source or destination sequence, get the list of sequences, get
the retransmission state of those messages that are in the queue, the
current acknowledgement range for a given sequence, etc. There is also
a method to suspend and resume the retransmission of messages assigned
for a specific source sequence.
There are two automatic test classes in trunk:
ManagedRMManagerTest in rt/ws/rm verifies the registration of these
managed RMManager and RMEndpoint beans.
ManagedEndpointsTest in systests/ws-spec verifies the functionality of
various methods of these beans.
These methods provided currently are the first cut. And I would like
to get your feedback and suggestion.
Thanks.
regards, aki
Re: JMX instrumentation for WS-RM checked in
Posted by Daniel Kulp <dk...@apache.org>.
On Wednesday, August 24, 2011 8:01:17 PM Aki Yoshida wrote:
> Thanks.
> I will still be working on it for a while and finalize some details. I
> thought it would be nice to get some feedback.
> By the way, do you already have some specific time in your mind for 2.5.0?
I'm thinking around October. That would keep the 6 month release schedule
which I'm a fan of.
Dan
>
> Regards, aki
>
> 2011/8/24 Daniel Kulp <dk...@apache.org>:
> > On Wednesday, August 24, 2011 1:30:30 PM Aki Yoshida wrote:
> >> Hi,
> >> I checked in an implementation of JMX instrumentation for the WS-RM
> >> components in trunk.
> >
> > This is really cool. :-)
> >
> > I added it to the new features for 2.5:
> > https://cwiki.apache.org/confluence/display/CXF20DOC/2.5+Migration+Guide
> >
> >
> > Thanks!
> > Dan
> >
> >> In short, RMManager and RMEndpoint objects have their instrumentation
> >> beans and various inspection methods into the internal states of the
> >> runtime artifacts such as RM source and destination sequences, the
> >> status of the message retransmission are exposed over these beans.
> >>
> >> To get an idea, you can simply activate JMX for your bus configuraiton
> >> and use jconsole to connect to the server. If your bus activates the
> >> reliable messaging feature, you will see the managed RMManger entry.
> >> The corresponding RMEndpoint entry will be registered when the
> >> endpoint is used.
> >>
> >> Most instrumentation methods are accessible from this managed
> >> RMEndpoint instance. For example, you can display the current state of
> >> a given source or destination sequence, get the list of sequences, get
> >> the retransmission state of those messages that are in the queue, the
> >> current acknowledgement range for a given sequence, etc. There is also
> >> a method to suspend and resume the retransmission of messages assigned
> >> for a specific source sequence.
> >>
> >> There are two automatic test classes in trunk:
> >> ManagedRMManagerTest in rt/ws/rm verifies the registration of these
> >> managed RMManager and RMEndpoint beans.
> >> ManagedEndpointsTest in systests/ws-spec verifies the functionality of
> >> various methods of these beans.
> >>
> >> These methods provided currently are the first cut. And I would like
> >> to get your feedback and suggestion.
> >>
> >> Thanks.
> >> regards, aki
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://dankulp.com/blog
> > Talend - http://www.talend.com
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com
Re: JMX instrumentation for WS-RM checked in
Posted by Aki Yoshida <el...@googlemail.com>.
Thanks.
I will still be working on it for a while and finalize some details. I
thought it would be nice to get some feedback.
By the way, do you already have some specific time in your mind for 2.5.0?
Regards, aki
2011/8/24 Daniel Kulp <dk...@apache.org>:
> On Wednesday, August 24, 2011 1:30:30 PM Aki Yoshida wrote:
>> Hi,
>> I checked in an implementation of JMX instrumentation for the WS-RM
>> components in trunk.
>
> This is really cool. :-)
>
> I added it to the new features for 2.5:
> https://cwiki.apache.org/confluence/display/CXF20DOC/2.5+Migration+Guide
>
>
> Thanks!
> Dan
>
>
>> In short, RMManager and RMEndpoint objects have their instrumentation
>> beans and various inspection methods into the internal states of the
>> runtime artifacts such as RM source and destination sequences, the
>> status of the message retransmission are exposed over these beans.
>>
>> To get an idea, you can simply activate JMX for your bus configuraiton
>> and use jconsole to connect to the server. If your bus activates the
>> reliable messaging feature, you will see the managed RMManger entry.
>> The corresponding RMEndpoint entry will be registered when the
>> endpoint is used.
>>
>> Most instrumentation methods are accessible from this managed
>> RMEndpoint instance. For example, you can display the current state of
>> a given source or destination sequence, get the list of sequences, get
>> the retransmission state of those messages that are in the queue, the
>> current acknowledgement range for a given sequence, etc. There is also
>> a method to suspend and resume the retransmission of messages assigned
>> for a specific source sequence.
>>
>> There are two automatic test classes in trunk:
>> ManagedRMManagerTest in rt/ws/rm verifies the registration of these
>> managed RMManager and RMEndpoint beans.
>> ManagedEndpointsTest in systests/ws-spec verifies the functionality of
>> various methods of these beans.
>>
>> These methods provided currently are the first cut. And I would like
>> to get your feedback and suggestion.
>>
>> Thanks.
>> regards, aki
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
> Talend - http://www.talend.com
>
Re: JMX instrumentation for WS-RM checked in
Posted by Daniel Kulp <dk...@apache.org>.
On Wednesday, August 24, 2011 1:30:30 PM Aki Yoshida wrote:
> Hi,
> I checked in an implementation of JMX instrumentation for the WS-RM
> components in trunk.
This is really cool. :-)
I added it to the new features for 2.5:
https://cwiki.apache.org/confluence/display/CXF20DOC/2.5+Migration+Guide
Thanks!
Dan
> In short, RMManager and RMEndpoint objects have their instrumentation
> beans and various inspection methods into the internal states of the
> runtime artifacts such as RM source and destination sequences, the
> status of the message retransmission are exposed over these beans.
>
> To get an idea, you can simply activate JMX for your bus configuraiton
> and use jconsole to connect to the server. If your bus activates the
> reliable messaging feature, you will see the managed RMManger entry.
> The corresponding RMEndpoint entry will be registered when the
> endpoint is used.
>
> Most instrumentation methods are accessible from this managed
> RMEndpoint instance. For example, you can display the current state of
> a given source or destination sequence, get the list of sequences, get
> the retransmission state of those messages that are in the queue, the
> current acknowledgement range for a given sequence, etc. There is also
> a method to suspend and resume the retransmission of messages assigned
> for a specific source sequence.
>
> There are two automatic test classes in trunk:
> ManagedRMManagerTest in rt/ws/rm verifies the registration of these
> managed RMManager and RMEndpoint beans.
> ManagedEndpointsTest in systests/ws-spec verifies the functionality of
> various methods of these beans.
>
> These methods provided currently are the first cut. And I would like
> to get your feedback and suggestion.
>
> Thanks.
> regards, aki
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com