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

Problem with lost DB-Connection

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

  • Problem with lost DB-Connection

    Hello all,

    I have some channels that read from a DB and send HL7-Messages using LLP. The problem is that sometimes the DB-Server (which is not on the same physical machine) should be restarted, so my channels loose the DB-connection and run no more(state=stopped), even if the DB-Server already runs afterwards.

    How to optimize the channels so that they check if the DB-Server is already there and if is there to set his state to "started"?

    Regards and thanks,

    Svetlomir.

  • #2
    Re:Problem with lost DB-Connection

    Hi Svetlomir,

    if the goal is periodically checking the DB connection status to restart the channels, you may:

    define a new channel, with JS Reader and JS Writer. In the JS Reader specify the checking interval (every X seconds, or every day at XX:AA AM).

    In the JS writer destination, put a code like the "stop&go" example in the wiki, to check if any of the DB channels is stoped and start them.

    hope that helps.

    Comment

    Working...
    X