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

Is there a way to handle channel close as fatal? #135

Open
me23 opened this issue Feb 12, 2019 · 0 comments
Open

Is there a way to handle channel close as fatal? #135

me23 opened this issue Feb 12, 2019 · 0 comments

Comments

@me23
Copy link

me23 commented Feb 12, 2019

Hi,

we haven a microservice running in docker. if rabbitmq dies (or if i kill it with docker kill)
Seneca exit with StatusCode 1. Which then stops the docker container. We run it with restart=always
so that the docker tries to restart the microservice. After rabbitmq comes back the service registered it self on rabbitmq like expected.

If i use docker stop or restart instead of kill. Then seneca exit with StatusCode 0. Now docker don't recognize the container in a fail state and therefor no restart occurs. Which will end up in the container running but without the service listening on rabbitmq anymore.

Is there a way to configure a channel close to exit the process with StatusCode > 0?
Or are there better ways of doing it?

Thank you
me23

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

No branches or pull requests

1 participant