On Tue, 17 Feb 2004, Tim Cutts wrote:
Subject: Re: Odd timeouts talking to MySQL 4.0, but not 3.x
On 17 Feb 2004, at 16:32, Jochen Wiedmann wrote:
Tim Cutts wrote:
where we are seeing the same problem (dropped connections after 8
hours):
Most probably you are not observing *dropped* connections but are using
a current version of DBD::mysql, which is not *reconnecting*
automatically,
if the *server* drops a connection after 8 hours. Beginning with 2.9002
2.9002 has a memory leek in bind_param()/execute(), so you might want to
upgrade to 2.9003 if you are going to be keeping connexions around for a
long time.
you need to enable the mysql_auto_reconnect flag. See the drivers
documentation for details.
Yes, I realise that, but *why* is the server dropping the connection
after 8 hours? Our settings of the wait_timeout and
interactive_timeout should enable connections to live for about a month
(and indeed on MySQL 3 servers, that is the case). I'm slightly scared
If using the same version of DBD::mysql, 4.x drops after 8 hours, which
happens to be the default timeout for mysql servers, and 3.x does not, I'd
be inclined to look to the server as the source of the problem.
Rudy
5 messages in com.mysql.lists.perlRe: Odd timeouts talking to MySQL 4.0...