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

Using mysql instead of Derby for mirth

  • Filter
  • Time
  • Show
Clear All
new posts

  • Using mysql instead of Derby for mirth


    I'm a bit confused. I read some posts in this forum telling me about problems when using the embedded database mirth uses by default.
    Could anyone give me more explanations? What is the risk for my production servers?
    How do I switch to mysql for instance?
    How do I switch a production server to mysql?

    Thank you,


    Post edited by: Bleupomme, at: 05/09/2008 08:04

  • #2
    Re:Using mysql instead of Derby for mirth

    If you're not storing message data, then there is probably no need to worry. If you are, then your database will grow and your system will slow. We recommend postgresql as the backend database, and all of our appliances use it. You should just be able to install postgresql, run the database schema script, and then switch your database properties over to postgresql. This can be done from the server manager or the .properties files.
    Jacob Brauer
    Director, Software Development
    NextGen Healthcare



    • #3
      Re:Using mysql instead of Derby for mirth

      Does anyone have experience doing the same with SQL Server 2005? How does it perform?


      • #4
        Re:Using mysql instead of Derby for mirth


        I have tried to use mysql but the schema script gives me errors. Postgresql is not an option for us. Please help.
        There were two alter table statements that made errors. I deleted them. Is that ok?


        Post edited by: Bleupomme, at: 05/13/2008 01:19


        • #5
          Re:Using mysql instead of Derby for mirth

          I tried this with a mysql database. Everything seems to work but sometimes I get weird errors or warnings like:

          WARN (com.webreach.mirth.plugins.messagepruner.MessageP runerService:226): could not prune message database
          com.webreach.mirth.server.controllers.ControllerEx ception: com.ibatis.common.jdbc.exception.NestedSQLExceptio n:
          --- The error occurred in mysql/mysql-channel.xml.
          --- The error occurred while executing query.
          --- Check the

          SELECT *

          FROM CHANNEL

          --- Check the SQL Statement (preparation failed).
          --- Cause: com.mysql.jdbc.exceptions.MySQLNonTransientConnect ionException: No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error: