intermittent network errors, which seems like the
only really valid use case for you.
- -chris
-Original Message- From: Christopher Schultz
[mailto:ch...@christopherschultz.net] Sent: Tuesday, August 12,
2014 8:28 PM To: Tomcat Users List Subject: Re: Question on Tomcat
JDBC Connection Pool
On 19/08/14 16:26, Christopher Schultz ch...@christopherschultz.net
wrote:
On 8/18/14, 1:05 PM, Wes Clark wrote:
One of the primary conditions for which we want to mark the
connection for death is when a rollback fails with an exception.
An example of this kind of error is a network error.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bertrand,
On 8/19/14, 2:23 PM, Bertrand Renuart wrote:
On 19/08/14 16:26, Christopher Schultz
ch...@christopherschultz.net wrote:
On 8/18/14, 1:05 PM, Wes Clark wrote:
One of the primary conditions for which we want to mark the
...@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
-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
that.)
When a SQL exception occurs, often the database connection will be
broken and should be evicted from the pool.
I'm
