JMX support

[rbieniek <Ra...@vodafone.com>]

Hello,

I'm currently considering the addition of some JMX support to AXIS. I plan
to add support for tunrning many handlers (etc. pp.) into MBeans which can
later be managed from a JMX-aware management application.

The JMX mechanics themselve are clear and I already have pretty good view
how to tackle this aim.

The only thing is wether I try to enroll this into Beta 3 or should I better
wait for an upcoming Beta 4 or RC1 release. I think I will have to touch
quite a bunch of files and therefore the merging effort is not to be
underestimated.

Any good ideas ?

Thanks in advance,

RB

AW: JMX support

[rbieniek <Ra...@vodafone.com>]

> > The only thing is wether I try to enroll this into Beta 3 or
> should I better
> > wait for an upcoming Beta 4 or RC1 release. I think I will have to touch
> > quite a bunch of files and therefore the merging effort is not to be
> > underestimated.
>

> What kind of MBeans do you plan to use ? If you use model mbeans ( and
> eventually commons-modeler ) the changes will be minimal. If you use
> dynamic mbeans ( eventually introspection-magic ) the changes are even
> smaller.
>
I haven't decided on that yet - I am not sure wether model mbeans will meet
my requirements. Though I must admit, I hadn't seen commons-modeler yet but
it seems pretty helpful.

> The only case that requires touching files is the standard mbeans, and
> I think it's not the best choice.
>
I perfectly agree with you there - it wasn't my intent anyway.

I came up with the JMX idea lately as I wrote a handler for
database-persistent AXIS sessions.
This handler keeps keeps Sessions around in memory for a configurable amount
of time and then it purges them from its internal cache. The sessions are
persisted when a message travels up the response chain (persisted or purged
in the onFault method,configurable) and restored on the request chain as
needed. The handlers purges outdated session in the database after a
configurable amount of time.
In real life I need to gather statistical performance data and to perform
some management operations like a forceful purge of all sessions.
Thats where JMX kicks in for me.

I admit there are little management issues on a simple handler like
SimpleSessiion. Nevertheless AXIS should provide some framework for the easy
implementation of MBeans for complex handlers. At least I'd like to monitor
the status of a deployed AXIS servlet and gather performance data on the
execution of web services.

RB

Re: JMX support

[co...@covalent.net]

On Fri, 26 Jul 2002, rbieniek wrote:

> I'm currently considering the addition of some JMX support to AXIS. I plan
> to add support for tunrning many handlers (etc. pp.) into MBeans which can
> later be managed from a JMX-aware management application.
> 
> The JMX mechanics themselve are clear and I already have pretty good view
> how to tackle this aim.
> 
> The only thing is wether I try to enroll this into Beta 3 or should I better
> wait for an upcoming Beta 4 or RC1 release. I think I will have to touch
> quite a bunch of files and therefore the merging effort is not to be
> underestimated.

What kind of MBeans do you plan to use ? If you use model mbeans ( and
eventually commons-modeler ) the changes will be minimal. If you use
dynamic mbeans ( eventually introspection-magic ) the changes are even 
smaller. 

The only case that requires touching files is the standard mbeans, and
I think it's not the best choice.

Costin