Allow the Donkey connection pool to separate into "read only" and "read/write" pools

[rbeckman-nextgen]

• There exist new optional settings in mirth.properties to:

  • Enable read/write pool splitting Include the channel / channel group / code template / code template library caches in either the read or write pools Set JDBC connection information for the read only pool ** Database type (may be different than the write pool) URL Driver Max connections Username Password * Pool type The read only pool may connect with the exact same settings as the read/write pool, essentially allowing segregated connection pools for message processing and user actions

  • When Mirth Connect starts up, if either the read only or read/write connections cannot be made, the startup process will halt and the server will stop.

Imported Issue. Original Details: Jira Issue Key: MIRTH-4346 Reporter: narupley Created: 2018-12-12T11:59:18.000-0800

[rbeckman-nextgen]

`# If true, various read-only statements are separated into their own connection pool.

• By default the read-only pool will use the same connection information as the master pool,
• but you can change this with the "database-readonly" options. For example, to point the
• read-only pool to a different JDBC URL:
• database-readonly.url = jdbc:...

• database.enable-read-write-split = true`

Imported Comment. Original Details: Author: narupley Created: 2018-12-12T11:59:37.000-0800