Announcement

Collapse

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

reprocess an error message

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

  • reprocess an error message

    I send a message to a hl7 server that some time give me this type of error:

    ERROR-408: MLLP Connector error
    ERROR MESSAGE: Timeout waiting for ACK

    Then the message goes to the error queue.
    If I manually select this message and I reprocess the message will be send.

    Is it possible to automatically reprocess the error message?

    Thank,

    Claudio

  • #2
    Re:reprocess an error message

    No.

    It could be an interesting option for the LLP channel "reprocess ACK timeouts" Could you add it to the JIRA?

    Comment


    • #3
      Re:reprocess an error message

      I have added it.

      Bye,
      Claudio

      Comment


      • #4
        Re:reprocess an error message

        The jira team close it, saying that I can use javascript.

        In which way?

        Thanks,

        Claudio

        Comment

        Working...
        X