Dennis Bekkering skrev:
A validation query doesn't help in the MySQL scenario: The driver will
automatically reconnect and successfully execute the query, but the
Connection still has a chance of remaining in an inconsistent state. This
won't happen on every reconnect, just on some.
You are
Martin,
Thanks for the help. As usual i was to fast with conclusions, my problems at
the time originated from a connection leak.
Thanks,
Dennis
2006/8/8, Martin Kalén [EMAIL PROTECTED]:
Dennis Bekkering skrev:
A validation query doesn't help in the MySQL scenario: The driver will
Hi Dennis,
Dennis Bekkering wrote:
Hello Tom,
Hmm, I'm not too sure why you need this behavior, but I think you
should definitely ask the DBCP guys over at the commons-user mailing
list.
I checked OJB.properties and I am using ConnectionFactoryPooledImpl.class .
I kill the connections with
Hello Armin,
I'm confused. How does this happen. OJB always use
ConnectionFactory#lookupConnection to lookup connections and doesn't
differ between transactional and non-transactional connections, thus the
validation query is always performed.
The only difference is the lifetime of the
Hello Tom,
Hmm, I'm not too sure why you need this behavior, but I think you
should definitely ask the DBCP guys over at the commons-user mailing list.
I checked OJB.properties and I am using ConnectionFactoryPooledImpl.class .
I kill the connections with the mysql administrator tool,
On 7/24/06, Dennis Bekkering [EMAIL PROTECTED] wrote:
I checked OJB.properties and I am using ConnectionFactoryPooledImpl.class .
I kill the connections with the mysql administrator tool, simulating timed
out connections. I discovered that the validation query is not called on non
transactional
On 7/21/06, Dennis Bekkering [EMAIL PROTECTED] wrote:
I am experiecing problems with mysql regarding connection time outs again.
This problem cannot be resolved by the pool settings provided or jdbc driver
settings such as autoReconnect (wich should not be used anyhow). Here is a
more detailed
