I've been using mirth connect from about a year ago in various environments with a very satisfactory result .
But now I've found a very worrying problem, I comment...
We have several mirth servers running, each connected to your DB, on another IP (external).

The problem occurs when one of the channels is working ( collect or send messages ) and a loss of communication occurs,
preventing access to the database of mirth .
At this time, the mirth begins to generate an error message " java.sql.SQLRecoverableException : error E / S ... "
per channel running .... normal...
But when communication with the database is restored, the mirth is not able to recover.
It is locked, the Web client does not respond or the console. You can only kill the process .
On the other hand when the connection loss occurs only in the channel usually it recovers when communication is restored

Can you implement some mechanism of reconnection with mirth DB error if communication with database ?