cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <>
Subject More on JMX integration
Date Fri, 23 Dec 2005 16:43:37 GMT
Hash: SHA1

I've committed initial support for JMX in the CoreServiceManager 
and ComponentInfo classes (and a helper classes as well as).

Next step would be how the MBean ObjectNames should be computed. Those 
names are normally used to narrow a JMX Consoles output to things one 
wants to see.

The MBean ObjectName is divided into a Domain and a Name part.

The Domain is just a word. I've choose 'Cocoon' as the default but this 
can be overridden by a jmx-domain attribute either in the root element 
of a component configuration file (and therefor acts as default for all 
components in that file) or at the individual component definition 
element itself. Of course included xconf files will inherit their parent 

The Name part is composed of comma separated key/value pairs. Finding a 
rational set of key/value pairs as default is questionable. The current 
implementation uses the FQCN of the component implementation class as 

FQCN:  org.apache.cocoon.impl.Comp

will result in an ObjectName name part:


Of course this can be overwritten by a attribute callen jmx-name.

Before I'm going to commit the real MBean I have I'd like to discuss 
whether we want to have a option to start a jetty 
with a JMX-Agent activated.

My oppinion would be: Yes we should

If most people find this is a must I'd further want to discuss whether 
we should switch to a more recent jetty version (now 4.2.23, I suggest 
using 5.1.8) which has better configuablility (we can get rid of the 
Loader class) and the way how JMX is configured is mutch clearer to me.

Also my oppinion on this is: Yes, I'd like to

- -- 
Giacomo Pati
Otego AG, Switzerland -
Orixo, the XML business alliance -
Version: GnuPG v1.4.2 (GNU/Linux)


View raw message