Sorry... my bad. My math doesn't work early in the morning. :-[
At any rate, the validation query run every minute is still acting as a
keep-alive on the connection. It'll never go stale. Personally I'd
drop the testWhileIdle, timeBetweenEvictionRuns, minEvictableIdleTime
and just let the
Jacob Rhoden wrote:
I am having the seemingly common Broken pipe to mysql problem with
tomcat.
Resource auth=Container name=jdbc/blah type=javax.sql.DataSource
maxActive=5 removeAbandoned=true
maxIdle=2 maxIdleTime=300 idleConnectionTestPeriod=60
maxWait=1 username=blah
If you read through
http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html,
you'll find the validationQuery attribute is used to test connections
before they are borrowed from the pool. The query can be as simple as
select 1.
As a side note, drop the autoReconnect=true from your
Thanks for your reply, I have read through that document and the one on
the mysql website, and discovered these other parameters, so I added
this as well. It didnt make any difference. The mysqladmin program still
reports the connections going untouched for hours.
validationQuery=select
-Original Message-
From: Jacob Rhoden [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 8:44 AM
To: Tomcat Users List
Subject: Re: Mysql timouts...
I will have to read the documents to find out why having the connection
automatically reconnected if there was a problem
David Smith wrote:
I think I see what's happening here. You've told the database pool to
continually test connections every hour. The validation query itself
validationQuery=select 1 testWhileIdle=true
timeBetweenEvictionRunsMillis=6
minEvictableIdleTimeMillis=6
I am having the seemingly common Broken pipe to mysql problem with
tomcat.
All i could find was some info about a maxideltime setting and
idleconnectiontestperiod where can I find out info about tuning to
make sure tomcat doesn't serve out stale database connections? The
following settings
