Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 39618 invoked from network); 6 Feb 2004 13:32:51 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 6 Feb 2004 13:32:51 -0000 Received: (qmail 17801 invoked by uid 500); 6 Feb 2004 13:32:40 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 17786 invoked by uid 500); 6 Feb 2004 13:32:40 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 17761 invoked from network); 6 Feb 2004 13:32:40 -0000 Received: from unknown (HELO mail01.solnet.ch) (212.101.4.135) by daedalus.apache.org with SMTP; 6 Feb 2004 13:32:39 -0000 Received: from localhost (localhost [127.0.0.1]) by mail01.solnet.ch (Postfix) with ESMTP id 793C562368 for ; Fri, 6 Feb 2004 13:32:40 +0000 (GMT) Received: from localhost ([127.0.0.1]) by localhost (mail01.solnet.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33796-08 for ; Fri, 6 Feb 2004 13:32:39 +0000 (GMT) Received: from wega-informatik.ch (adsl-business-212-101-24-127.solnet.ch [212.101.24.127]) by mail01.solnet.ch (Postfix) with ESMTP id 1093362367 for ; Fri, 6 Feb 2004 13:32:39 +0000 (GMT) Message-ID: <40239777.1080103@wega-informatik.ch> Date: Fri, 06 Feb 2004 14:32:39 +0100 From: =?ISO-8859-1?Q?=22Dirk_R=FCttgers=2C_wega_Informatik_AG=22?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en, de-de, de-ch MIME-Version: 1.0 To: commons-user@jakarta.apache.org Subject: [dbcp] Howto monitor JDBC Connections on tomcat 4.1.29 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by SolNet 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 I'd like to monitor the number of active / idle JDBC Connections on tomcat 4.1.29. Is there a (tomcat) build in tool, script, log where i can find more information on how the pool works, and which resources are used? Are there any JAVA/Servlet/JSP/Taglib Sources which can be used to monitor activities or check at least the pool dynamically? At our site the the JDBC Connection is defined as a JNDI Datasource in the server.xml DefaultContext as follows factory org.apache.commons.dbcp.BasicDataSourceFactory driverClassName oracle.jdbc.driver.OracleDriver url jdbc:oracle:thin:@... maxActive 200 maxIdle 40 maxWait 10000 ... Thanks for your kind help. Dirk -- ________________________________________________________ wega Informatik AG www.wega-informatik.ch Gartenstrasse 56 Tel. +41 61 270 87 87 CH-4052 Basel Fax. +41 61 270 87 88 Dr. Dirk R�ttgers Dirk.Ruettgers@wega-informatik.ch ________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org