cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <Ralph.Go...@digitalinsight.com>
Subject RE: Instrumentation, anyone?
Date Thu, 04 Mar 2004 16:47:41 GMT
There were some posts on February 4 that indicated that excalibur-instrument
was a good way to get info on the pools was excalibur-instrument-manager
(and presumably excalibur-instrument). Your earlier post indicated that
avalon instrumentation is dead. Are these the same things?

Ralph

 -----Original Message-----
From: 	Carsten Ziegeler [mailto:cziegeler@s-und-n.de] 
Sent:	Thursday, March 04, 2004 8:32 AM
To:	dev@cocoon.apache.org
Subject:	RE: Instrumentation, anyone?


> 
> I'm no JMX expert at all, but I understand that basic JMX 
> support can be easily "piggybacked" on existing code, as long 
> as you're basically happy with monitoring and small 
> management tasks: more important needs might require 
> significant changes to the code base, so if I were to draw a 
> plan I would say that we _might_ include some JMX code right 
> now and that we _should_ plan JMX support for 2.2, even if 
> that requires some refactoring. I have the feeling that a 
> complex application like Cocoon really could use some 
> management tools.
> 
Sounds like a good plan!

Carsten

Mime
View raw message