The _isconnected function of dbcon returns true on stale connections (disconnected, but no tcp_reset event broadcasted to the client because it doesn't know its disconnected), even after a query fails with the error message "the mysql server has gone away"
The fact it does it even after a query fails is the main thing that bugs me.
ID:1823614
 Apr 3 2015, 4:09 am
|
|||||||||||||
| |||||||||||||
|
Apr 3 2015, 5:36 am
|
|
Lummox JR
   |
The code governing this is pretty old and is one of the spots I'm less familiar with. As a workaround for now, I would suggest that if you do have a query fail, look at the error message and reconnect + retry it if it's a "gone away" message.
|
And in my case, sqls aren't done that often, but the world never stops or has to restart, i just close the connection and re-open it on every query.
| |