New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support MySQL servers sending OK packet to QUIT sequence #1277
Comments
Hi! I'm not really sure what the ask here is. This module simply implements a client that works with the MySQL protocol, as defined by the MySQL documentation. If you are running against a custom MySQL that has an altered protocol, you're just going to have to fork this module and modify it to function with the modified MySQL protocol. |
@dougwilson thank you reply.
|
A connection close is the FIN packets you are seeing, and what we expect, as documented. |
but maybe some server side response a OK_Packet, we should call which API to send "FIN" packets? |
this._socket.close() ? |
Is your server sending an OK packet after the QUIT packet? I can look to see if we handle that currently (it has never been an issue with this driver before), but there's no saying if that will solve your problem unless you confirm first if your server is sending the OK packet. |
yes, our mysql server response OK_packet when receive the quit Protocal |
Ok, I have updated this issue to be a feature request. PR is welcome to implement the feature. |
thanks |
The OK packets are supported now in the current master code. Please install the master and test to confirm if this fixes your issue. You can find the install instructions for testing at https://github.com/felixge/node-mysql#install |
maybe it result in new issue, when the connection count archive the max pool count, it can't create the new connection. |
server throw: 504 Gateway Time-out |
Hi @kidyfirst , I'm not sure what you are saying, I'm sorry. Can you provide a PR to address this, or even a full program I can use to reproduce the issue? |
sorry, our mysql can't access by outnet on dev and github can't snapshot. |
Well, if I don't have a way to reproduce the issue to debug it, there unfortunately isn't much I can do but await a PR from you to fix the issue. |
ok, i can locate the issue by myself, thank your help , can your provide the mail? i can send the snapshot to your. |
i got the mail. |
@dougwilson
I found the process that the node-mysql client to discount the connection as follow.
1, client send mysql packet with "request quit" to server.
2, server reply a "fin" packet to client.
3, client replay a "fin" packet to server.
right?
but now, my company's mysql make some customization, server will ignore the "request quit" packet.
it will not notify client to send "fin" packet. the node-mysql can add one option to let client to release the connection?
The text was updated successfully, but these errors were encountered: