Skip to content
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

Open connections prevent process to close #51

Open
claustres opened this issue Feb 3, 2020 · 1 comment
Open

Open connections prevent process to close #51

claustres opened this issue Feb 3, 2020 · 1 comment
Labels

Comments

@claustres
Copy link
Member

Steps to reproduce

Create a distributed application and use it through mocha tests

Expected behavior

The process should close at the end of the tests

Actual behavior

The process does not close due to connections that are still open, ie service publisher/subscriber on the app. This is not really annoying when launching a long-lived server but it is for running tests.

There can also be timeouts running linked to publicationDelay and coteDelay.

It seems that cote components exhibits a close() method that should be called to clean up. We could also keep track of the timeout objects to cancel it. Should we provide a global colseDistribution() at app level or provide individual functions to clear app/service-level timeouts/components ?

System configuration

Tell us about the applicable parts of your setup.

Module versions (especially the part that's not working): 0.7

NodeJS version: 8.16

Operating System: Windows

@claustres claustres added the bug label Feb 3, 2020
@claustres claustres self-assigned this Feb 3, 2020
@claustres
Copy link
Member Author

If we remove the --exit flag in our own mocha tests the problem appears.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant