[MIRTH-4335] Add stricter error catching to the source/destination queue threads Created: 23/Oct/18  Updated: 06/Nov/18  Resolved: 06/Nov/18

Status: Closed
Project: Mirth Connect
Component/s: Donkey, Server
Affects Version/s: None
Fix Version/s: 3.7.0, 3.6.2

Type: Improvement Priority: Minor
Reporter: Nick Rupley Assignee: Nick Rupley
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


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.

Generated at Wed Nov 20 02:26:56 PST 2019 using JIRA 6.2.7#6265-sha1:91604a8de81892a3e362e0afee505432f29579b0.