Mirth Connect
  1. Mirth Connect
  2. MIRTH-4335

Add stricter error catching to the source/destination queue threads

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.7.0, 3.6.2
    • Component/s: Donkey, Server
    • Labels:
      None

      Description

      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.

        Activity

          People

          • Assignee:
            Nick Rupley
            Reporter:
            Nick Rupley
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development