If a non-default driver is used for the main read/write pool and the database-readonly.driver is empty, it still uses the default driver instead of delegating to the one specified in database.driver.
Workaround:
Explicitly set database-readonly.driver as well in mirth.properties.
If a non-default driver is used for the main read/write pool and the database-readonly.driver is empty, it still uses the default driver instead of delegating to the one specified in database.driver.
Workaround: Explicitly set
database-readonly.driver
as well in mirth.properties.Imported Issue. Original Details: Jira Issue Key: MIRTH-4414 Reporter: narupley Created: 2019-05-08T15:16:36.000-0700