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 barry.l.propes@citi.com
 designates 67.231.145.106 as permitted sender)
From: "Propes, Barry L " <barry.l.propes@citi.com>
To: "'Tomcat Users List'" <users@tomcat.apache.org>
Date: Wed, 4 Apr 2012 08:53:26 -0500
Subject: RE: jdbc pool properties
Thread-Topic: jdbc pool properties
Thread-Index: Ac0SYQE2KboBKmAhRzWabvfCRTiqKAACK46Q
Message-ID: 
 <08382548D50D3049BD5599E1E3146B3416F43AC1A8@exgtmb06.nam.nsroot.net>
References: 
 <CAG2rwuNhHZUZYe2=wzgUkT4XdwWrgSv5gRm=S4ydymAMXGVG+A@mail.gmail.com>
 <17972289.150.1333543571938.JavaMail.daniel@cleveland>
In-Reply-To: <17972289.150.1333543571938.JavaMail.daniel@cleveland>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

There are some databases that do go in and periodically kill off connection=
s, aside from the Tomcat settings.

In addition to testOnBorrow=3Dtrue, I also had two other attributes, but no=
t sure if Tomcat 7.0 uses them or not, as I'm on 6.0.29.

    testOnBorrow=3D"true"
    timeBetweenEvictionRunsMillis=3D"-1"
    minEvictableIdleTimeMillis=3D"28800"


-----Original Message-----
From: Daniel Mikusa [mailto:dmikusa@vmware.com]
Sent: Wednesday, April 04, 2012 7:46 AM
To: Tomcat Users List
Subject: Re: jdbc pool properties


----- Original Message -----
> My db connections seem to be lost after an extended period of
> inactivity

There could be a number of reasons that this occurs.  Perhaps a network iss=
ue is causing them to be disconnected or the database may be timing them ou=
t.  At any rate, it's not likely that the problem would be caused by the "r=
emoveAbandoned" / "abandonedTimeout" settings, unless you application is no=
t properly returning connections to the connection pool.

  https://tomcat.apache.org/tomcat-7.0-doc/jndi-datasource-examples-howto.h=
tml#Preventing_database_connection_pool_leaks


> (for a web application).  And the only way to get the connections to
> work again is to restart tomcat.
>
> My tomcat.jdbc.pool.Datasource settings have:
>
>  <property name=3D"maxActive" value=3D"100"/>
>         <property name=3D"maxIdle" value=3D"30"/>
>         <property name=3D"maxWait" value=3D"1000"/>
>         <property name=3D"defaultAutoCommit" value=3D"true"/>
>         <property name=3D"removeAbandoned" value=3D"true"/>
>         <property name=3D"removeAbandonedTimeout" value=3D"60"/>
>

You probably want to add testOnBorrow=3D"true" and "validationQuery=3DSELEC=
T 1"  (or some other valid query for your DB).  See the following link for =
an explanation of those properties.

  https://commons.apache.org/dbcp/configuration.html

This will cause your connections to be validated prior to their use by your=
 application.  Stale connections will be removed and replaced with new, wor=
king connections.

>
> Is it the removedAbonded and abandonedTimeout?  Does it mean "after 60
> seconds, remove the connection from the pool?

No.  See either of the links I've referenced above for an explanation of th=
ese settings.

>
> I guess what I need is a minActive setting then?
>

There's no "minActive" setting.  You have "minIdle", but I don't think that=
 would help here.

Dan


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


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