Announcement

Collapse

Mirth Connect 4.0.1 Released!

Mirth Connect 4.0.1 is now available as an appliance update and on our GitHub page. Mirth Connect 4.0.1 is a patch release containing a bug fix which includes fixing a Jetty keystore regression that caused Connect servers using a PKCS12 keystore containing a wildcard certificate and/or a certificate with a SAN to throw an exception on startup. 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

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

  • persistent queues

    Should I be using persistent queues? When we first started playing with Mirth we were told to not user persistent queues. We are have to manually resend many messages a day due to ack timeouts even after setting the timeouts to 50000ms.
    Is anyone using persistent queues for this reason?
    Regards,
    chris

  • #2
    Reersistent queues

    PQ are a secure issue. Try it for a few days and then, decide.

    On the other hand, you can make a few changes into Mirh code to re-send messages with an ACK timeout.

    Comment


    • #3
      What exactly is "Use Persistent Queues" doing?

      Comment


      • #4
        In a nutshell, turning on persistent queues sets a channel to "messages stay in the queue until they're delivered", instead of "try X number of times, then fail". I usually turn on persistent queues when the recipient is through a VPN that gets a little flaky at times...

        Comment

        Working...
        X