Skip to content

Live Query Server does not shut down properly #4593

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

Closed
acinader opened this issue Feb 28, 2018 · 1 comment
Closed

Live Query Server does not shut down properly #4593

acinader opened this issue Feb 28, 2018 · 1 comment

Comments

@acinader
Copy link
Contributor

acinader commented Feb 28, 2018

Issue:
ctrl-c kills the parse-server, but not the live-query server.

This issue arises when:

  1. I am doing local cloud code development on my laptop.
  2. I am running the live-query server in the same process as the parse server. Starting server with npm start
  3. When I try to cycle the parse-server using ctrl-c (SIGINT) or kill pid (SIGKILL) the process for the livequery server doesn't die. Attempts to restart the server with npm start will fail with a port in use message (Unable to listen on port 8082. The port is already in use.).
  • Server
    • parse-server version (Be specific! Don't say 'latest'.): true on 2.7 and master
    • Operating System: osx 10.13.4
    • Hardware: mbp (late 2016)
    • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): localhost
@acinader acinader changed the title Add shutdown hook for live-query server Remove special handling for sigint and sigkill Mar 16, 2018
@acinader acinader changed the title Remove special handling for sigint and sigkill Live Query Server does not shut down properly Mar 16, 2018
@stale
Copy link

stale bot commented Sep 18, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Sep 18, 2018
@stale stale bot closed this as completed Sep 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant