cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Corin Moss" <>
Subject Instrumentation / JMX (Was RE: New Sitemap Treeprocessor for 2.2 [Instrumentation / JMX Now])
Date Sun, 21 Mar 2004 00:50:12 GMT


I guess the first step would be to look at the code for the Excalibur
instrumentation-client - which is all I've been using. 

I'm probably preaching to the choir, but to get a quick look at what's
already there, just run (from your Cocoon root directory):

build start-instrumentation-client 

>From looking at the range of info available, it would make sense to wrap
the current instrumentation interfaces. In fact, I guess it would be
fairly trivial to wrap the instrumentation "listener" component
(apologies - I don't know its correct name) so that the current
instrumentation would report all its samples to the Mbean (which would
act as an instrumentation client in this case.) 

Now, I wouldn't suggest the above as a long term strategy, but if we're
interested in getting JMX into an upcoming release, it might just be the
easiest way to proceed (provided that current instrumentation provides
all the info we want.)

Time for a new thread I guess ;)

-----Original Message-----
From: Ralph Goers []
Sent: Sunday, 21 March 2004 12:39 p.m.
To: ''
Subject: RE: New Sitemap Treeprocessor for 2.2 [Instrumentation / JMX

I think it is a matter of who can get to it first.  I'm just getting
started on figuring out how to instrument our product. Part of this will
be to gather whatever Cocoon is already making available.  I haven't had
a chance to really figure out how to interface with the Instrumentation
stuff so it would be helpful to know what you are doing and if there is
some sample code I could leverage. I'd like to "wrap" the already
instrumented stuff with Mbeans.


-----Original Message-----
From: Corin Moss []
Sent: Saturday, March 20, 2004 4:13 PM
Subject: RE: New Sitemap Treeprocessor for 2.2 [Instrumentation / JMX

Ahh, ok, it seems that I missed the JMX thread:

I've been using Instrumentation quite successfully for a couple of
weeks, it was how I managed to pick up a bug in the CIncludeTransformer,
and it's helped hugely in some fairly complex pool debugging that we're
doing now.  I see that a few people have offered to implement JMX - is
there any progress on this? I'd love to help.

CAUTION: This e-mail and any attachment(s) contains information
that is intended to be read only by the named recipient(s). It
may contain information that is confidential, proprietary or the
subject of legal privilege. This information is not to be used by
any other person and/or organisation. If you are not the intended
recipient, please advise us immediately and delete this e-mail
from your system. Do not use any information contained in it.

For more information on the Television New Zealand Group, visit
us online at

View raw message