Skip to content

3.2.0 Upgrade Guide

Chris Turczynskyj edited this page Nov 3, 2021 · 3 revisions

JRE 1.6 (Java 6) is no longer supported as of version 3.2.0. If you are still using JRE 1.6, please ensure you update to at least JRE 1.7 before upgrading to Mirth Connect 3.2.0+. However future releases in the 2.x, 3.0.x, and 3.1.x branches will still continue to support JRE 1.6 unless otherwise stated.

The default connection pool used for message processing has been updated to HikariCP. We've seen that HikariCP is generally faster and more reliable than DBCP although this change should be imperceptible to most users. Support for DBCP still exists and users can revert back to it if necessary by adding the following line to mirth.properties and restarting the server.

database.pool = dbcp

A bug in the configuration map was fixed where certain special characters were not being handled correctly. Since this bug affected both the saving and loading of the configuration map, there is a chance your configuration map values will be loaded differently after upgrading Mirth Connect. Please verify your configuration map values after upgrading.

Clone this wiki locally