rbeckman-nextgen
commented
4 years ago This could be very useful for users that experience JRE related bugs that wont have a fix until a major Mirth Connect patch.
For example, a user could run into bug MIRTH-2109 and be on a system that needs to have Java 7 as default for other applications. This implementation could allow the user to set the MIRTH_JRE_HOME variable and run the mirth connect server using Java 6. MIRTH-2109 wont see a fix until 2.2 or 3.0 which would leave no resolution to a user until its release.
-Eduardo Armendariz
Imported Comment. Original Details: Author: eduardoa Created: 2013-04-15T12:38:10.000-0700
When installing Mirth on Windows, the current installer automatically chooses the JRE/JDK based on defined min/max versions if there are multiple Java runtimes installed. There can be breaking changes between major releases of the Java runtime and it can be helpful to be able to specify the exact Java runtime for an application/service.
Install4J supports 2 different methods of manually specifying the runtime when there is more than one runtime installed. The first is to run the setup using the "manual" parameter. The second is to define an environment variable the specifies the path to java.exe. The current Mirth setup does not support the second option which prevents a full unattended installation in this scenario.
Ideally Mirth should reference the "MIRTH_JRE_HOME" environment variable (if present) for the JRE that should be used. This supported by Install4J and detailed on page 77 of the user's manual (http://resources.ej-technologies.com/install4j/help/doc/help.pdf#page=76).
Imported Issue. Original Details: Jira Issue Key: MIRTH-2509 Reporter: srowe Created: 2013-04-15T11:22:13.000-0700