You can configure torque to use the
org.apache.torque.dsfactory.SharedPoolDataSourceFactory. Set
torque.dsfactory.torque.pool.testOnBorrow true. Provide a
torque.dsfactory.torque.pool.validationQuery. This setting up will
guarantee every connection returned from the pool is a good one.
Andras Balogh wrote:
Hello,
This is a MySQL related prolbem You must specify autoreconnect=true
(or something like) that at connection
properties. You will find this info on the mysql site, jdbc connection
properties.
Best regards,
Andras.
Matthew P. Reath wrote:
I'm developing a web-based application using Tomcat/Torque/MySQL. The
problem I run into is that after 8 hours of inactivity the persistent
connection Torque uses becomes invalid and I get an exception. The
next time
I try it works. After another 8 hours of idle time the process repeats.
I searched the internet for answers but most of them involved good
programming practice to handle this situation in one's own JDBC code, I
however am using Torque.
Is there a way to configure Torque to handle this timeout period? I'd
rather
not depend on the connection always being there in case it was dropped
because of network problems or what not. Ideally I would like Torque to
reconnect anytime it's connection becomes invalid or do some sort of
heartbeat.
Thanks,
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
