Skip to content

Error: This socket is closed. #538

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
Closed
strk opened this issue Mar 14, 2014 · 2 comments
Closed

Error: This socket is closed. #538

strk opened this issue Mar 14, 2014 · 2 comments

Comments

@strk
Copy link
Contributor

strk commented Mar 14, 2014

An exception is thrown on client.query() if the connection was closed due to stream error. See #537 (comment)

I guess an event should be raised instead...
@brianc
Copy link
Owner

brianc commented Oct 20, 2014

Can you give an example of how to reproduce this?

@strk
Copy link
Contributor Author

strk commented Oct 20, 2014

untested:

  • call connect, wait for "onConnect" event.
  • kill the backend (pg_ctl stop)
  • invoke an arbitrary query using client.query(), wait for "onError" event

The event is never sent, an exception is thrown by client.query instead

@brianc brianc closed this as completed Jun 16, 2017
@pihvi pihvi mentioned this issue Jun 22, 2023
Open
@doron2402 doron2402 mentioned this issue Jun 26, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brianc @strk