These actions seems to incorrectly conflated in the code. I'd also like to do
the same thing, so if you get it working, keep me posted.
-Original Message-
From: Iris Hupkens [mailto:i.hupk...@topdesk.com]
Sent: Wednesday, December 03, 2014 5:14 AM
To: 'users@tomcat.apache.org'
Subject:
...@christopherschultz.net]
Sent: Tuesday, August 12, 2014 8:28 PM
To: Tomcat Users List
Subject: Re: Question on Tomcat JDBC Connection Pool
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Wes,
On 8/12/14, 5:26 PM, Wes Clark wrote:
(If the answer differs between Tomcat 7 and Tomcat 8, please note
(If the answer differs between Tomcat 7 and Tomcat 8, please note that.)
When a SQL exception occurs, often the database connection will be broken and
should be evicted from the pool. In our code, we call this marking the
connection for death. We do this because we don't want to set the
:07 PM
To: Tomcat Users List
Subject: Re: Tomcat JDBC Connection Pool initialization question
On 23. Juli 2014 01:20:27 MESZ, Wes Clark wcl...@guidewire.com wrote:
I want to initialized a new connection being added to the pool with
more than one SQL statement. I cannot see how to override
I want to initialized a new connection being added to the pool with more than
one SQL statement. I cannot see how to override the existing methods to do
this. Has anyone done this, or have a suggestion for me?
