The server has been running with the new settings for a couple of days
now and it looks good so far.
Thanks everyone for your help!
-Stijn
Stijn de Witt wrote:
Martin Kalén wrote:
Stijn de Witt wrote:
Could you review these settings for the evictor thread solution? Do
you think these settings
Martin Kalén wrote:
Stijn de Witt wrote:
Could you review these settings for the evictor thread solution? Do
you think these settings are ok?
validationQuery=select 1
minEvictableIdleTimeMillis=6
timeBetweenEvictionRunsMillis=12
numTestsPerEvictionRun=10
testWhileIdle=true
Martin Kalén wrote:
So you should never combine autoReconnect for MySQL JDBC URL and
testOnBorrow
for a Commons Pool-based Connection pool (like OJB's default- and
DBCP-based
pools). If you do, you will just create additional overhead by
checking the
same things twice.
The advantage of
Stijn de Witt wrote:
The advantage of mastering the Commons Pool options is that this will
work with all database servers that OJB supports, not just MySQL.
Do you know if the autoReconnect=true option alone will fix it? I have
seen mention of autoReconnectForPools option? We are not planning
Stijn de Witt wrote:
We have developed a web application using OJB. All seems to work fine,
but after some hours of being deployed we run into a problem.
snip/
java.io.EOFException
at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1394)
snip/
I have seen a number of solutions mentioned:
1)
Hi,
(...)
Now I am getting a bit lost in all these options, and testing them is
very hard. Does anyone here have experience with this issue and know of
an easy way to fix it? Option 1) with autoReconnect seems most
attractive to me, but how should I set such a connection parameter using
OJB?
Danilo Tommasina wrote:
Now I am getting a bit lost in all these options, and testing them is
very hard. Does anyone here have experience with this issue and know
of an easy way to fix it? Option 1) with autoReconnect seems most
attractive to me, but how should I set such a connection parameter
