[CORE-246] Entries being written to the PM user session log at the same time will cause a query to error Created: 14/Dec/16 Updated: 29/Jun/17 Resolved: 14/Jun/17 |
|
| Status: | Closed |
| Project: | i2b2 Core Software |
| Component/s: | CRC Cell, PM Cell |
| Affects Version/s: | 1.7.08b |
| Fix Version/s: | 1.7.09 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Janice Donahoe | Assignee: | Janice Donahoe |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| i2b2 Sponsored Project/s: |
i2b2 Core
|
| i2b2 Related Project/s: |
BBP
|
| Affects Database/s: |
All databases
|
| Participant/s: |
| Description |
|
When writing to the PM user session log, the set login attempt needs to use the database timestamp instead of the calendar.getInstance().getTime(). This will prevent queries from generating an error when trying to write to the log at the same time.
Part of the problem is the PM user session log has a primary key in which two entries cannot have the same user and date-time. When a query runs it is the service account that is logged as the user. So if two or more people are running a query (ontology, setfinder, pdo, etc) and the crc is trying to write to the log at the exact same time, then only one entry will file and the other entries will error because the system thinks it is a duplicate. Temporary work around is to delete the constraint on the log. |
| Comments |
| Comment by Janice Donahoe [ 14/Jun/17 ] |
| This issue has been fixed and will be included in release 1.7.09. |