Announcement

Collapse

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

Persistent queues vs. automatic database pruning

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Persistent queues vs. automatic database pruning

    A bit o' clarification and confirmation is required... (I could set up a test to figure this out myself, but just asking the question is easier!)

    Say I have a channel with an LLP destination that occasionally goes away (network unreachable, etc.) The channel has persistent queueing enabled, but also has auto-prune set to three days.

    Does the auto-prune only apply to messages that have been sent, or does it also affect queued messages (in the .mule directory as recently explained to me) as well?

    Want to make sure that if the LLP destination isn't reachable for several days, pending messages won't be discarded.

    Thanks, Mike

  • #2
    Re:Persistent queues vs. automatic database pruning

    Prune only applies to db.

    The .mule messages are as save as your hard disk can defeat from the General failure assaults.

    Comment


    • #3
      Re:Persistent queues vs. automatic database prunin

      Cool - that's what I was hoping.

      Thanks

      Comment

      Working...
      X