Mirth Connect 4.1.0 Released!

Mirth Connect 4.1.0 is now available as an appliance update and on our GitHub page. Mirth Connect 4.1.0 includes new features such as new event log messages, additional fields to the Welcome to Mirth Connect screen, new information included in alerts as well as many smaller changes, updates, and improvements. This release also contains several 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

Error polling psql db and freeze

  • Filter
  • Time
  • Show
Clear All
new posts

  • Error polling psql db and freeze

    Hello everyone,

    I'm Jacopo and I'm testing Mirth functionalities.

    In last months I've been trying to poll data from cloud PostgreSQL db and produce DICOM in order to generate worklist.
    I'm using Docker image nextgenhealthcare/connect:3.9.0-jdk.

    All works fine for weeks, but sometimes the database reader fails with next error and remains freezed in polling until container restarting (I cannot restart/stop/halt only the channel):

    ERROR (com.mirth.connect.connectors.jdbc.DatabaseReceive rQuery:207): An error occurred while polling for messages, retrying after 10000 ms...
    org.postgresql.util.PSQLException: The connection attempt failed.
    at org.postgresql.core.v3.ConnectionFactoryImpl.openC onnectionImpl(
    at org.postgresql.core.ConnectionFactory.openConnecti on(
    at org.postgresql.jdbc.PgConnection.<init>(PgConnecti
    at org.postgresql.Driver.makeConnection( 04)
    at org.postgresql.Driver.connect(
    at java.sql/java.sql.DriverManager.getConnection(DriverManager .java:677)
    at java.sql/java.sql.DriverManager.getConnection(DriverManager .java:228)
    at com.mirth.connect.connectors.jdbc.DatabaseReceiver Query.initSelectConnection(DatabaseReceiverQuery.j ava:340)
    at com.mirth.connect.connectors.jdbc.DatabaseReceiver Query.poll(
    at com.mirth.connect.connectors.jdbc.DatabaseReceiver .poll(
    at torJob.execute(
    at 13)
    at org.quartz.simpl.SimpleThreadPool$ ( by: connect timed out
    at java.base/ Method)
    at java.base/
    at java.base/
    at java.base/
    at java.base/ ava:403)
    at java.base/
    at org.postgresql.core.PGStream.<init>( 61)
    at org.postgresql.core.v3.ConnectionFactoryImpl.openC onnectionImpl(
    ... 12 more

    Now, I'm avoiding retries, since channel works periodically.
    I don’t think it is a problem of db reachability because other services continue to work, at least I would like to avoid the polling freeze after fails.

    Has this happened to anyone yet?
    Hoping someone can help me to find the reason.

    Thank you so much


  • #2
    That is a problem of database reachability.

    You can try shelling Into the container and use traditional network tools to attempt to debug connectivity.
    Diridium Technologies, Inc.