Important! Fixed underlying network socket unexpected silent death.
Important! Fixed underlying network socket unexpected silent death.

In production at rare (once at 2-3 days) occasion mysql-5.6.11-win-x64 unexpectedly closes socket. Situation is similar when I just forcibly kill mysqld process. 

Next, Protocol.destroy() called very silently because of socket pipe, and all consequent queries return with error code  'PROTOCOL_ENQUEUE_AFTER_DESTROY'.

Suggested disconnectHandler doesn't work out due to 'false' value at the error flag fatal.

Error message 'PROTOCOL_ENQUEUE_AFTER_DESTROY' in such situation seems to be misleading, since there was no user-code invocation on Connection.destroy(), and, moreover the connection to the server is already gone.

Suggested patch supposed to fix this and assumes unexpected socket close as 'PROTOCOL_CONNECTION_LOST'.

I am checking it on my env right now.

Thanks!
zhhb/node-mysql,WY08271/node-mysql,mysqljs/mysql,chinazhaghai/node-mysql,saisai/node-mysql,Jimbly/node-mysql,NikosEfthias/node-mysql,yourcaptain/node-mysql,seangarner/node-mysql,AndersonGitHub/node-mysql,yanninho/node-mysql,bORm/node-mysql,cgvarela/node-mysql,mhasan3/node-mysql,bbito/node-mysql,danidomi/node-mysql,XiaoLongW/node-mysql,yan5845hao/node-mysql-1,grooverdan/node-mysql,tempbottle/node-mysql,theblackperl/node-mysql,linalu1/node-mysql,felixge/node-mysql,yulongge/node-mysql,l371559739/node-mysql,apathyjade/node-mysql,shipci/node-mysql,teng2015/node-mysql,AshWilliams/node-mysql,ashwinks/node-mysql,acorbi/node-mysql,wxkdesky/node-mysql,lukw00/node-mysql