Mirth Connect 4.3.0 Released!

Mirth Connect 4.3.0 is now available as an appliance update and on our GitHub page.

This is a major release containing new features like adding new functionality to the Mirth Connect Setup Wizard, adding the ability for resource and channel-specific classloaders to load child-first or parent-first, and added a default implementation of the getObjectsForSwaggerExamples() method in the ServicePlugin class. This release also contains enhancements for the Mirth Connect Administrator Launcher, the Mirth Connect Docker images, and several bug fixes and security improvements.

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

  • 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.


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

      Cool - that's what I was hoping.