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.

Sign up for GitHub

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

Jump to bottom

Abort connection using pool in aws lambda #2378

Closed

lajpatshah opened this issue Jul 18, 2020 · 0 comments

Labels

lajpatshah commented Jul 18, 2020

Hello

We were testing mysql connection in aws lambda. Following was our observation and need your help.

using non-pool connection when I end the connection, I never get abort connection error in mysql console log.
using pool with end connection option then i receive following error in mysql.
[Note] Aborted connection 57 to db: 'dbanme' user: 'username' host: 'x.x.x.x' (Got an error reading communication packets)

Aborted connection happens immediately after calling pool.end().

Can anybody help me why mysql throws this error?

Thanks

lajpatshah closed this as completed

dougwilson added the question label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment