Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of billdsd@gmail.com designates
 216.239.58.191 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=FmyZ0n2shn4XYifcXafWDSekUPVet6WihlsUBtQ7i+te7uUDVUVNnrftcMn+4Q4o9i
         TEdukAYcsGdwxrp/+WRPcopKJpEQa3cmk2k0GnxlFkeBLGN4f1oBOY97HZRWRYvZ6fEO
         qYU49uzhPbDr/HY6ZDhIKLetxuOobtY5Xk+h4=
Message-ID: <4AE7443A.7000701@gmail.com>
Date: Tue, 27 Oct 2009 12:04:26 -0700
From: Bill Davidson <billdsd@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: DBCP woes (running out of cursors).
References: <4AD615CD.1050005@gmail.com>
	 <4AD88C61.2090700@christopherschultz.net>
 <4AD8D930.50502@gmail.com>	 <4AD8E300.5020006@gmail.com>
 <4AD8E75A.8040503@gmail.com>	 <4ADC7B07.3070701@christopherschultz.net>
 <4ADCBAB1.2000006@gmail.com>	 <4ADCBE1A.30003@christopherschultz.net>
 <4AE5F208.9030607@gmail.com>	 <4AE6005F.7090901@apache.org>
 <b97771c60910261801s2bd324c4r75c55425afbd15ad@mail.gmail.com>
In-Reply-To: <b97771c60910261801s2bd324c4r75c55425afbd15ad@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Elli Albek wrote:
 >2. If your JDBC driver supports caching of prepared statements and
 >metadata, do it in the driver and disable this in DBCP. IMO DBCP does
 >a poor job at best in caching. We use mysql and its JDBC driver is
 >doing an excellent job.

It didn't occur to me that that was available.

 >3. Your JDBC driver may already be caching metadata that DBCP is
 >caching. In this case you are caching the same data twice. Make sure
 >it dose not happen, it is a big memory overload on the JVM.

Interesting.  I need to do more research.

 >B. Avoid hot deployment of apps by shutting down tomcat before
 >updates. This is safer, but also not 100% clean.

We're actually doing that already, but for other reasons.  We currently
have different servers for different parts of the world and schedule down
time for off-peak periods for the regions they serve.

Thanks for the info.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org