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

Message keeps coming back.

  • Filter
  • Time
  • Show
Clear All
new posts

  • Message keeps coming back.

    Can anyone recreate this, or give me some explanation:

    I have a channel with an llp destination connector, using persistent queues.
    In the dashboard I right click the channel and choose send message. I open a file containing an adt message and click process messages. The message gets queued. In this case the server on the recieving end is down, so Mirth correctly keeps retrying. After several minutes I right click the channel and choose remove all messages. The queue gets set to 0 and there are no messages in the channel.

    If I deploy all channels, after about a minute, all of a sudden the message I thought I deleted reappears in the channel queue. I can remove it again, but if I ever deploy the channel it comes back. Am I doing something wrong?

  • #2
    Re:Message keeps coming back.

    This is because the REAL queue is kept in the .mule directory. If you want to remove it, you have to manually remove the content of this directory.

    The QUEUE status at Dashboard is not full-synchronized with the file queue.


    • #3
      Re:Message keeps coming back.

      Ok, I deleted the files from the mule directory and they haven't come back. Thanks for the tip. But if the persistent queue is held in the file system, what is the message table in sql for?


      • #4
        Re:Message keeps coming back.

        You're right, this is a pending issue.