Announcement

Collapse

Mirth Connect 4.0.1 Released!

Mirth Connect 4.0.1 is now available as an appliance update and on our GitHub page. Mirth Connect 4.0.1 is a patch release containing a bug fix which includes fixing a Jetty keystore regression that caused Connect servers using a PKCS12 keystore containing a wildcard certificate and/or a certificate with a SAN to throw an exception on startup. 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

Trouble talking to MySQL 8

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

  • Trouble talking to MySQL 8

    Evening all,

    I am having trouble getting Mirth Connect to talk to MySQL 8. I am trying to write to a database. Code is fine on MySQL 5.7.28

    Running Mirth 3.12 in Docker.
    Running MySQL 8.0.26 in Docker

    Database Driver is com.mysql.cj.jdbc.Driver
    URL is jdbc:mysql://192.168.0.12:3306/patient_hl7?allowPublicKeyRetrieval=true&sslMode=D ISABLED
    I am usin the Get Tables trick to make sure I can access the database. This works fine on MySQL 5.7

    However if I run a MySQL 8.0.26 docker image using the same connection string then I dont get an error connecting to it, but nothing is returned in the Get Tables view.
    I know the "allowPublicKeyRetrieval" bit is needed as without it, I get an exception in Mirth Connect. We also use that on our SQL connection string from within our own product to talk to the database in C#. Basically, I know the URL is correct.

    Works on MySQL 5.7 but nothing returned on MySQL 8.

    Any ideas where I can start looking?
    Are there log files in Mirth somewhere in the Docker image? (I am new to Mirth - taking over an existing system from another developer)

    Thanks in advance

    Mat

  • #2
    shell into the container and see /opt/connect/logs/mirth.log
    Diridium Technologies, Inc.
    https://diridium.com

    Comment


    • #3
      Nothing in the logs that looks out of place

      INFO 2021-11-23 21:13:39,635 [Main Server Thread] com.mirth.connect.server.Mirth: Mirth Connect 3.12.0 (Built on September 2, 2021) server successfully started.
      INFO 2021-11-23 21:13:39,639 [Main Server Thread] com.mirth.connect.server.Mirth: This product was developed by NextGen Healthcare (https://www.nextgen.com) and its contributors (c)2005-2021.
      INFO 2021-11-23 21:13:39,639 [Main Server Thread] com.mirth.connect.server.Mirth: Running OpenJDK 64-Bit Server VM 11.0.12 on Linux (5.10.60.1-microsoft-standard-WSL2, amd64), derby, with charset UTF-8.
      INFO 2021-11-23 21:13:39,640 [Main Server Thread] com.mirth.connect.server.Mirth: Web server running at http://172.17.0.3:8080/ and https://172.17.0.3:8443/

      Comment


      • #4
        Running 5.7.31 in Docker (and not changing anything in Mirth) works. So I have to assume that the issue is talking to MySQL 8 as 5.7 works fine.

        Comment


        • #5
          I replied to your github post at https://github.com/nextgenhealthcare...scussions/4873.
          Diridium Technologies, Inc.
          https://diridium.com

          Comment

          Working...
          X