If you use Oracle, some DBCP settings may not work and you may need to
use Oracle connection pool classes.
In particular, I was not able to use DBCP and have a loginTimeout when
using Oracle.
Using Oracle connection pool classes, the validation query does not
work in the same way as in Apache DBCP
Mark Eggers wrote:
> When the database is shut down, I get exception messages logged (you do log
> exceptions, right?). Pages that depend on database content are missing that
> content.
>
> When the database is started up again, a refresh of the pages displays the
> content coming from the data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
On 2/24/2011 12:08 PM, David Smith wrote:
> With tomcat's built-in database pooling, just adding a validation query
> to the resource config should be all that's necessary. On each borrow
> of a connection, the connection is tested and closed
- Original Message (edited)
From: Michael Ludwig
János Löbb schrieb am 24.02.2011 um 11:24 (-0500):
> On Feb 24, 2011, at 10:58 AM, David kerber wrote:
> > On 2/24/2011 10:49 AM, János Löbb wrote:
> >>
> >> What is the very basic structure of a web application that is
> >> connected to
; Date: Fri, 25 Feb 2011 20:09:00 +0100
> From: mil...@gmx.de
> To: users@tomcat.apache.org
> Subject: Re: programming question
>
> János Löbb schrieb am 24.02.2011 um 11:24 (-0500):
> > On Feb 24, 2011, at 10:58 AM, David kerber wrote:
> > > On 2/24/2011 10:49 AM, Já
János Löbb schrieb am 24.02.2011 um 11:24 (-0500):
> On Feb 24, 2011, at 10:58 AM, David kerber wrote:
> > On 2/24/2011 10:49 AM, János Löbb wrote:
> >>
> >> What is the very basic structure of a web application that is
> >> connected to a database through a connection pool, but would not
> >> req
On 2/24/2011 11:35 AM, chris derham wrote:
When I mention them that their programs should handle the situation
resulting from the database bounce automagically and not the dba handling
the web app or Tomcat shutdowns and restarts, they look at me like I came
from Mars or Saturn :-)
If you cod
With tomcat's built-in database pooling, just adding a validation query
to the resource config should be all that's necessary. On each borrow
of a connection, the connection is tested and closed if the test fails.
Failed connections are replaced with new ones.
--David
On 2/24/2011 10:49 AM, Ján
>
> When I mention them that their programs should handle the situation
> resulting from the database bounce automagically and not the dba handling
> the web app or Tomcat shutdowns and restarts, they look at me like I came
> from Mars or Saturn :-)
>
If you code the app to use a connection pool,
On Feb 24, 2011, at 10:58 AM, David kerber wrote:
> On 2/24/2011 10:49 AM, János Löbb wrote:
>> Hi,
>>
>> What is the very basic structure of a web application that is connected to a
>> database through a connection pool, but would not require to restart itself
>> or restart Tomcat when the da
On 2/24/2011 10:49 AM, János Löbb wrote:
Hi,
What is the very basic structure of a web application that is connected to a
database through a connection pool, but would not require to restart itself or
restart Tomcat when the database goes down - let say for maintenance ?
Telling otherwise how
11 matches
Mail list logo
