Hello Ben!
I am in no ways a socket expert, so I can only provide a general remark
and pass on what I got from hearsay (below):
When pursuing such things, please provide information about the
operating systems used, client/server assignment etc.
Gleb Paharenko wrote:
Hello.
MySQL usually waits some time for data from client even if connection
is broken, because MySQL could no nothing about it. [[...]]
> Also different xxx_timeout variables are influenced as well.
another job, a cron job, that Kills this script/connection if it takes more
than 2 minutes. I was just wondering if this would leave the connection
open in MySQL.
Yes, in my opinion, this could be the cause of your problem.
I heard that when a process terminates on a Unix style system, its open
sockets are closed by the OS; this also applies to forceful termination
by a killing signal. Then, the communication partner will be informed
about the socket being closed and can terminate the connection.
On Windows systems, this closing was said not to happen, so a socket
remains open unless the process really closed it, and timeout detection
on the other side is the only way out.
So information about the OSs and machines involved may be significant to
judge the situation.
Regards,
Jörg
--
Joerg Bruehe, Senior Production Engineer
MySQL AB, www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
