Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 36162 invoked from network); 7 Aug 2009 15:14:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Aug 2009 15:14:45 -0000 Received: (qmail 49130 invoked by uid 500); 7 Aug 2009 15:14:51 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 49051 invoked by uid 500); 7 Aug 2009 15:14:51 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 49040 invoked by uid 99); 7 Aug 2009 15:14:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Aug 2009 15:14:51 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [193.252.22.159] (HELO smtp5.freeserve.com) (193.252.22.159) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Aug 2009 15:14:40 +0000 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3402.me.freeserve.com (SMTP Server) with ESMTP id 13AAB1C00087 for ; Fri, 7 Aug 2009 17:14:20 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3402.me.freeserve.com (SMTP Server) with ESMTP id 05B5D1C00088 for ; Fri, 7 Aug 2009 17:14:20 +0200 (CEST) Received: from smtp.homeinbox.net (unknown [91.109.136.47]) by mwinf3402.me.freeserve.com (SMTP Server) with ESMTP id C311F1C00087 for ; Fri, 7 Aug 2009 17:14:19 +0200 (CEST) X-ME-UUID: 20090807151419799.C311F1C00087@mwinf3402.me.freeserve.com Received: from localhost (localhost [127.0.0.1]) by smtp.homeinbox.net (Postfix) with ESMTP id BB8781A4FA0 for ; Fri, 7 Aug 2009 16:14:18 +0100 (BST) X-Virus-Scanned: Debian amavisd-new at homeinbox.net Received: from smtp.homeinbox.net ([127.0.0.1]) by localhost (server01.dev.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s0cE6AYlD5jD for ; Fri, 7 Aug 2009 16:14:15 +0100 (BST) Received: from [192.168.0.9] (study03.dev.local [192.168.0.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.homeinbox.net (Postfix) with ESMTPSA id 8126B1A4F1C for ; Fri, 7 Aug 2009 16:14:15 +0100 (BST) Message-ID: <4A7C44C0.3040506@apache.org> Date: Fri, 07 Aug 2009 16:14:08 +0100 From: Mark Thomas User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: Regarding JmxRemoteLifecycleListener References: <200908071525.58184.rainer.frey@inxmail.de> <4A7C30F2.1030303@apache.org> <200908071640.36852.rainer.frey@inxmail.de> In-Reply-To: <200908071640.36852.rainer.frey@inxmail.de> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Rainer Frey (Inxmail GmbH) wrote: > On Friday 07 August 2009 15:49:38 Mark Thomas wrote: >> Rainer Frey wrote: >>> 1. Revision 751496 was commented with "Tomcat uses Platform MBean server. >>> Adjust listener accordingly." and removed the separate configuration >>> for "Catalina" mbean server and registry. Was this accompanied by a >>> change in tomcat itself, and if so, with which released tomcat version >>> does the current revision work? Or should I use an older revision with >>> released tomcat 6? >> You can either use an older version or patch Tomcat 6. >> http://svn.apache.org/viewvc?diff_format=h&view=rev&revision=677910 > > Thanks for the info, and the amzingly quick answer. Are there plans to add at > least this patch to tomcat 6? I will bundle the JmxListener with an > application that comes with a tomcat inside, and would prefer to use a binary > build for that. > >>> 2. Are there plans to add this listener to Tomcat 6 release? >> Not at present. > > Was it denied, or never proposed? I remember from messages on the user mailing > list you originally wanted to get this ready for 6.0.19. I never proposed it. I'll propose that and the Platform MBean simplification for 6.0.x later today. >>> 3. I think of trying to backport this to Tomcat 5.0 for our internal use. >>> Do you think this is possible/feasible without knowledge of tomcat code >>> level internals? What was the situation regarding the mbean servers then? >> It should be reasonably portable. The listener doesn't touch any Tomcat >> internals apart from the listener interface, the string manager and the >> logger. Fixing any issues should be simple. Worst case - delete the >> references. > > Again, I sould base it on the revision with the additional catalina mbean > server, right? Yes, unless you patch Tomcat. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org