Re: [Axis2] Management Interface - JMX Support

[Chathura Ekanayake]

On 3/24/06, Soumadeep <[EMAIL PROTECTED]> wrote:

Hi Chathura,

 

Few things…

1)       The ObjectName Axis2:name=org.apache.axis2.management.AxisGlobalsMBean is hard coded. Would it be ok if we put it in come configuration file. Can you please add another property to the ObjectName called type "domain:name=aaa,type=ttt" . Where type could be admin,stats etc. I know it's not mandatory but would be great if you can accommodate.

Yes, We can put the ObjectNames in a configuration file and add a type property. I will put the ObjectNames in a seperate XML file for now, and we can decide where to put them once the code is integrated (e.g. axis2.xml )

 

2)        I have noticed that you are following a different name convention for your Mbeans. As per the JMX spec, the name of the interface is appended by "MBean" , so xxxMBean would be the interface and xxx would be the class which implements the interface xxxMBean. 

hmm.. I was wrong. I will remove the "MBean" suffix from MBean implementations.

 

 For instance in your code e.g. public class AxisServicesMBean extends AbstractManagementInterface , where AbstractManagementInterface is an abstract class. Let me know if you have any particular reason for doing this.

MBean implementations use xxxManager classes in the management.core.managers package to perform management functionalities. Therefore, they use the methods provided by AbstractManagementInterface abstract class to obtain referances to xxxManager classes. So the MBeans do not depend on the method used to access core objects.

 

I am also assuming that you are using Standard MBeans

I am using Model MBeans and commons modeler package, which lets us create Model MBeans very easily.

 

 

3)       Could you also extend the MBeans with NotificationBroadcasterSupport for sending notifications?

Yes, I am thinking of doing this. But then, I can't extend them from AbstractManagementInterface abstract class and I have to implement the code to access core classes in the MBean itself. For now, I will extend notification MBeans from the NotificationBroadcasterSupport and we can discuss a proper way later. ( e.g. implementing the NotificationBroadcaster interface)

 

 

Do you maintain your code in some scratch area? Or you just put patches in the AXIS2 src (Obviously I am assuming you take a committers help to do so)

 

My code is the scratch area;

https://svn.apache.org/repos/asf/webservices/axis2/trunk/archive/java/scratch/Axis_Management_module/

 

 

 

 

Thanks

Soumadeep

 

-----Original Message-----
From: Chathura Ekanayake [mailto: [EMAIL PROTECTED]]
Sent: Friday, March 24, 2006 10:01 PM
To: axis-dev@ws.apache.org
Subject: [Axis2] Management Interface - JMX Support

 

 

Hi,

 

I have done some work in the JMX interface. I am sending it in the attached patch file.

Please commit the patch to the url;

https://svn.apache.org/repos/asf/webservices/axis2/trunk/archive/java/scratch

 

It currently supports configuring and monitoring support using commons modeler.

 

Monitoring functionalities are:

 

In message count

Out message count

In fault message count

Out fault message count

 

at all global, service and operation levels.

 

I am planning to implement JMX notifications as the next step.

Please give your ideas about possible events that should emmit notifications.

 

e.g. In message count exceeding some predefined value

 

Chathura.