I will try your suggestion now and see if there are any changes. Otherwise Im not sure, especially since Ive never hear about the behavior you describe. I make sure that correct parameters are sent, and did a lot of debugging, but the result is still the same. The only way I can answer is I would need to have a way to reproduce the issue, if you can provide full complete code with the MySQL DDL to use and instructions on how to reproduce. NodeJS : Cannot enqueue Handshake after invoking quitTo Access My Live Chat Page, On Google, Search for 'hows tech developer connect'I have a hidden feature. ![]() When I execute auth.login for the first time, it is working great, but on the second time, it returns the same result as from the first time, even if I change all the parameters. (C:\xampp\htdocs\projects\nodesrv\node_modules\httpdispatcher\httpdispatcher.js:69:15)ĭefine (, function ( db, localStorage, md5, $ ) ) connection mysql. at Protocol.validateEnqueue (/Users/anon/Desktop/project Web/nodemodules/mysql/lib/protocol/Protocol. Var query = conn.Error: Cannot enqueue Handshake after invoking quit.Īt Protocol._validateEnqueue (C:\xampp\htdocs\projects\nodesrv\node_modules\mysql\lib\protocol\Protocol.js:196:16)Īt Protocol._enqueue (C:\xampp\htdocs\projects\nodesrv\node_modules\mysql\lib\protocol\Protocol.js:129:13)Īt Protocol.handshake (C:\xampp\htdocs\projects\nodesrv\node_modules\mysql\lib\protocol\Protocol.js:52:41)Īt nnect (C:\xampp\htdocs\projects\nodesrv\node_modules\mysql\lib\Connection.js:123:18)Īt (C:\xampp\htdocs\projects\nodesrv\libs\auth.js:19:8)Īt C:\xampp\htdocs\projects\nodesrv\dispatcher.js:25:8Īt C:\xampp\htdocs\projects\nodesrv\node_modules\httpdispatcher\httpdispatcher.js:130:3Īt HttpChain.next (C:\xampp\htdocs\projects\nodesrv\node_modules\httpdispatcher\httpdispatcher.js:123:9)Īt doDispatch (C:\xampp\htdocs\projects\nodesrv\node_modules\httpdispatcher\httpdispatcher.js:58:13)Īt IncomingMessage. I am getting this error: Cannot enqueue Handshake after invoking quit. events.js:68 throw arguments 1 // Unhandled error event Error: Cannot enqueue Handshake after invoking quit. Route file on which I try to apply conn.end() var express = require('express') Ĭonsole.log(conn.state, conn.ThreadId) // authenticated, xxxx If you using the node-mysql module, just remove the. YouTube 0:00 / 2:42 MATHURA Error: Cannot enqueue Handshake after already enqueuing a Handshake. The Solution to Cannot enqueue Handshake after invoking quit is. I tried to query the MySQL database in Node.js but I dont know. Error: Cannot enqueue Handshake after already enqueuing a Handshake. I am starting to think that in some point the involvement of Passport.js configuration causes it because before the query I give conn.state and it seems that there is already an open connectionĮrror (events.js is not a file I work on, I guess is a standard node_modules factory file) `events.js:183Įrror: Cannot enqueue Quit after invoking quit. Node.js - MySQL - how to close connection (Cannot enqueue Query after invoking quit error). 1213 Closed anonprophet opened this issue on 7 comments anonprophet commented on added the label Sign up for free to join this conversation on GitHub. ![]() one time I even had Cannot enqueue Handshake after invoking quit now I’ve put my createConnection call back in my routes and everything is working I just don’t like the idea that I have to copy that stuff in every route making a query to the db. Apparently they pushed in unnecessary code in their last iteration that is also bugged. Error: Cannot enqueue Handshake after already enqueuing a Handshake. I guess the connection kind of gets screwed up.How can I fix this issue Best Solution If you using the node-mysql module, just remove the. The error you provided is because you are chronologically calling connection.query () after you called connection.end (). For a reason that I am struggling to find out, I cannot apply conn.end() after my queries in any route. Cannot enqueue Handshake after invoking quit I have tried not to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |