Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 14548 invoked from network); 7 Mar 2004 10:47:05 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 7 Mar 2004 10:47:05 -0000 Received: (qmail 71888 invoked by uid 500); 7 Mar 2004 10:46:36 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 71866 invoked by uid 500); 7 Mar 2004 10:46:35 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 71856 invoked from network); 7 Mar 2004 10:46:35 -0000 Received: from unknown (HELO web21404.mail.yahoo.com) (216.136.232.74) by daedalus.apache.org with SMTP; 7 Mar 2004 10:46:35 -0000 Message-ID: <20040307104649.91831.qmail@web21404.mail.yahoo.com> Received: from [203.143.133.7] by web21404.mail.yahoo.com via HTTP; Sun, 07 Mar 2004 02:46:49 PST Date: Sun, 7 Mar 2004 02:46:49 -0800 (PST) From: Giridharan Rajagopalan Subject: Re: Requirements on JMX API To: axis-dev@ws.apache.org In-Reply-To: <404A4F3A.10203@iseran.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-526577858-1078656409=:91589" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N --0-526577858-1078656409=:91589 Content-Type: text/plain; charset=us-ascii Steve: Few questions: >>enum registered services What might be the possible services that can be accorded in this? Some of my observations are: 1.Providers like RPCProvider and MsgProviders can be monitored. Included services are Message & Wrapped services. >>examine service config, change it, WSDD? >>usage logging of service load (and failures) Provide seperate interfaces for logging of service loads. Does this mean every request needs to be logged along with the action ? >>any other things worth monitoring to trigger management alerts. Can you be more specific on this? Thanks & Regards Giridharan Steve Loughran wrote: Giridharan Rajagopalan wrote: > Hi All: > > I am new to this group. > > Have been working in Axis for the past 1 year. > Could somone let me know the requirements on the JMX API that needs to > be done , as part of Administration & Monitoring of Axis. > > Few of my questions are: > > 1. Does this JMX API provide the user exit feature of adding custom API > handlers? if you want it :) > > 2. What are the components of Axis or webservice that needs to be > managed using this? Good question. I dont know. I'd expect the core bits of the system to be manageable to see what is going on, to examine and manipulate endpoint configuration, etc. Things that would be good -enum registered services -examine service config, change it, -usage logging of service load (and failures) -any other things worth monitoring to trigger management alerts. Client side monitoring would be useful too -if you have JMX management for your app, you want to be able to manage all of it. > > 3. Is there any framework design on the actual implementation? > No. But if you look at axis.management there is a class there that uses reflection to find the method in MX4J to register any object as a JMX management point. My goal was to add manageablility to base system components (probably through new interfaces or helper classes), but not make the core system dependent upon having JMX around. > I would luv to get things started on this requirement. > I think a lot of people would welcome JMX support. Assuming your own project needs JMX, your own requirements should provide a good focus for JMX integration. > Thanks & Regards > > giri > > > Please raise your voice against SCO Issue.Register and discuss NO2SCO at I think dims has already made his position on that entertainingly clear :) Please raise your voice against SCO Issue.Register and discuss NO2SCO at http://groups.yahoo.com/group/no2sco/ --------------------------------- Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster. --0-526577858-1078656409=:91589 Content-Type: text/html; charset=us-ascii
Steve:
 
Few questions:
 
>>enum registered services
 
What might be the possible services that can be accorded in this?
Some of my observations are:
 
1.Providers like RPCProvider and MsgProviders can be monitored.
Included services are Message & Wrapped services.

>>examine service config, change it,
 
WSDD?

>>usage logging of service load (and failures)
Provide seperate interfaces for logging of service loads.
Does this mean every request needs to be logged along with the action ?

>>any other things worth monitoring to trigger management alerts.
Can you be more specific on this?

Thanks & Regards
Giridharan

Steve Loughran <steve_l@iseran.com> wrote:
Giridharan Rajagopalan wrote:

> Hi All:
>
> I am new to this group.
>
> Have been working in Axis for the past 1 year.
> Could somone let me know the requirements on the JMX API that needs to
> be done , as part of Administration & Monitoring of Axis.

>
> Few of my questions are:
>
> 1. Does this JMX API provide the user exit feature of adding custom API
> handlers?

if you want it :)

>
> 2. What are the components of Axis or webservice that needs to be
> managed using this?

Good question. I dont know. I'd expect the core bits of the system to be
manageable to see what is going on, to examine and manipulate endpoint
configuration, etc. Things that would be good

-enum registered services
-examine service config, change it,
-usage logging of service load (and failures)
-any other things worth monitoring to trigger management alerts.

Client side monitoring would be useful too -if you have JMX management
for your app, you want to be able to manage all of it.

>
> 3. Is there any framework design on the actual implementation?
>

No. But if you look at axis.management there is a class there that uses
reflection to find the method in MX4J to register any object as a JMX
management point.

My goal was to add manageablility to base system components (probably
through new interfaces or helper classes), but not make the core system
dependent upon having JMX around.

> I would luv to get things started on this requirement.
>

I think a lot of people would welcome JMX support. Assuming your own
project needs JMX, your own requirements should provide a good focus for
JMX integration.

> Thanks & Regards
>
> giri
>
>
> Please raise your voice against SCO Issue.Register and discuss NO2SCO at

I think dims has already made his position on that entertainingly clear :)


Please raise your voice against SCO Issue.Register and discuss NO2SCO at

http://groups.yahoo.com/group/no2sco/

Do you Yahoo!?
Yahoo! Search - Find what you�re looking for faster. --0-526577858-1078656409=:91589--