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.

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

If a job gets terminated by the OS (out of memory exception), a broken process exception occurs which is not caught properly. #16

Closed
gowabash opened this issue Dec 31, 2018 · 0 comments
Closed

If a job gets terminated by the OS (out of memory exception), a broken process exception occurs which is not caught properly. #16

gowabash opened this issue Dec 31, 2018 · 0 comments

Comments

@gowabash
Copy link
Contributor

gowabash commented Dec 31, 2018 •
edited
Loading

This causes the worker to continue grabbing messages that then immediately fail because the process pool is broken.
@gowabash gowabash changed the title If a job gets terminated by the OS (out of memory exception), a broken process exception occurs which is not caugt properly If a job gets terminated by the OS (out of memory exception), a broken process exception occurs which is not caught properly. Dec 31, 2018
@gowabash gowabash mentioned this issue Dec 31, 2018
Merged
@cdrx cdrx closed this as completed Feb 8, 2020
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
@cdrx @gowabash