Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 77403 invoked from network); 4 Mar 2004 15:58:00 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Mar 2004 15:58:00 -0000 Received: (qmail 13876 invoked by uid 500); 4 Mar 2004 15:57:50 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 13829 invoked by uid 500); 4 Mar 2004 15:57:50 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 13816 invoked from network); 4 Mar 2004 15:57:50 -0000 Received: from unknown (HELO warden.diginsite.com) (208.29.163.248) by daedalus.apache.org with SMTP; 4 Mar 2004 15:57:50 -0000 Received: from wlvims01.diginsite.com by warden.diginsite.com via smtpd (for daedalus.apache.org [208.185.179.12]) with SMTP; Thu, 4 Mar 2004 07:57:52 -0800 Received: from WLVIMS01 ([127.0.0.1]) by WLVIMS01.digitalinsight.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with SMTP id com for ; Thu, 4 Mar 2004 07:57:51 -0800 Received: by calexc01.diginsite.com with Internet Mail Service (5.5.2657.72) id ; Thu, 4 Mar 2004 07:57:05 -0800 Message-ID: <31DF72A980E5D511B48C000102BD8685061DB26A@calexc01.diginsite.com> From: Ralph Goers To: "'dev@cocoon.apache.org'" Subject: RE: Instrumentation, anyone? Date: Thu, 4 Mar 2004 07:57:04 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Actually, I have a requirement to do exactly that, so if anyone has already done it I'd happily use the code. Ralph -----Original Message----- From: Gianugo Rabellino [mailto:gianugo@apache.org] Sent: Thursday, March 04, 2004 7:53 AM To: dev@cocoon.apache.org Subject: Instrumentation, anyone? It was a long time since I last used the Avalon instrumentation stuff, but it just seems like it's not working anymore. I'm following the provided instructions under tools/instrumentation, something is listening on port 15555 as expected but the GUI seems just to sleep in a "Not connected" status (and tcpdump shows very little, if any, traffic on that port). Am I overlooking something? More in general, I'm wondering what is the overall status of instrumentation and checking for community interest on this particular topic. I don't quite understand what is the status in Avalon-land of the instrumentation thingy, but it doesn't seem quite active. OTOH, I start to think that this proprietary instrumentation is a dead-end since it seems pretty clear that JMX is the way to go. I'm wondering if there is any interest (and kowledgeable people) in JMX-enabling Cocoon (for monitoring and management purposes only). I think that Cocoon deployments could benefit quite a bit from being properly instrumented. Opinions? -- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance - http://www.orixo.com (Blogging at: http://www.rabellino.it/blog/)