[CORE-129] Improve datasource validations Created: 17/Jul/14 Updated: 30/May/19 Resolved: 10/Apr/18 |
|
| Status: | Resolved |
| Project: | i2b2 Core Software |
| Component/s: | Install |
| Affects Version/s: | 1.7.00 |
| Fix Version/s: | 1.7.10 |
| Type: | Improvement | Priority: | Major |
| Reporter: | William Shuman | Assignee: | Janice Donahoe |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | wikirelease | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| i2b2 Sponsored Project/s: |
i2b2 Core
|
| Participant/s: |
| Description |
|
Currently i2b2 1.7 uses the following validations for its default installations which are not ideal.
<validation> <validate-on-match>false</validate-on-match> <background-validation>false</background-validation> </validation> If we encounter a situation in which a connection in the pool goes bad we will continue to use that connection which will cause errors in i2b2. The better solution would be to use validation. <validation> <validate-on-match>true</validate-on-match> <check-valid-connection-sql>SELECT 1 FROM DUAL</check-valid-connection-sql> <use-fast-fail>true</use-fast-fail> </validation> Obviously the sql will change per database engine but it should be easy to configure based on each of the datasources defined ie "SELECT 1" for MSSQL |
| Comments |
| Comment by Mike Mendis [ 07/Feb/18 ] |
| I have commit the changes and the new datasources on currently on our qa evniroments. |
| Comment by Janice Donahoe [ 10/Apr/18 ] |
| This change was made to the databases in the testing environment 3 months ago and was tested throughout the process of testing the 1.7.10 release. |