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

Add stricter error catching to the source/destination queue threads #4211

Closed
rbeckman-nextgen opened this issue May 11, 2020 · 0 comments
Closed
Milestone

Comments

@rbeckman-nextgen
Copy link
Collaborator

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

If an OutOfMemoryError or some other error of similar severity occurs, currently the queue threads will just abort, and I think an error will display in the server log.

As always, when OOMs start happening there's no guarantee that Connect (or any application) is going to be able to gracefully recover, especially if it causes RAM corruption.

However we can make a best-effort attempt by catching any Throwable and continuing to let the queue thread run, making sure to still send an error to the server log and possibly also an alertable error event.

Imported Issue. Original Details:
Jira Issue Key: MIRTH-4335
Reporter: narupley
Created: 2018-10-23T08:08:28.000-0700

@rbeckman-nextgen rbeckman-nextgen added this to the 3.7.0 milestone May 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.