obfscUser-lockOut-qryCancelled-2.png
obfscUser-lockOut-qryError.png
[WEBCLIENT-220] Web Client possible null pointer Created: 01/Dec/17 Updated: 14/Feb/18 Resolved: 02/Feb/18 |
|
| Status: | Closed |
| Project: | i2b2 Web Client |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.09c |
| Type: | Bug | Priority: | Major |
| Reporter: | Mike Mendis | Assignee: | Mike Mendis |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
obfscUser-lockOut-qryCancelled-2.png
obfscUser-lockOut-qryError.png
|
| Participant/s: |
| Description |
|
When canceling a query is the variable i2b2.CRC.ctrlr.deleteCurrentQuery is null than checking on a i2b2.CRC.ctrlr.deleteCurrentQuery.QM which result in a null pointer. Should check to see that i2b2.CRC.ctrlr.deleteCurrentQuery is not null first.
|
| Comments |
| Comment by Janice Donahoe [ 07/Dec/17 ] |
|
This is not working correctly.
In the Web Client the query appears to be cancelled. The query will appear in Show Query Status with a "Cancelled" status however when I look in the qt_query_master table it looks like the query was not cancelled. The query doesn't have a DELETE_DATE and the DELETE_FLAG is set to N. Also, an ERROR message is returned to the user instead of the locked out message. 2 screen shots attached obfscUser-lockOut-qryError.png – shows ERROR message returned obfscUser-lockOut-qryCancelled-2.png – shows query cancelled in Show Query Status This issue is being returned to development. |
| Comment by Janice Donahoe [ 02/Feb/18 ] |
| This was fixed and released in version 1.7.09c |