Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Resend messages when receiving system is back

  • Filter
  • Time
  • Show
Clear All
new posts

  • Resend messages when receiving system is back

    Working with Mirth 1.6

    We are sending messages to a Receiving system.

    Settings for our Destination channel are:

    Send Timeout(ms): 5000
    Reconnect Interval: 10000
    Keep Connection Open: No
    Maximum Retry Count: 50
    Use Persistent Queues: No

    Receiving system went down for four hours, When it came back on line, Mirth failed to resend the messages.

    Obviously the settings we have wouldn't accomodate resending the messages when the Receiving system came back up.

    But what is the correct settings to allow resending of messages after a connection comes back up?
    Is it simply Keep Connection Open ?
    What does Use Persistent Queues do?

    Whilst we want the facility for Mirth to Resend messages, is there any impact on system performance when Mirth is constantly trying to send messages for a down receiving connection?

    Many thanks Robin