Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.7.07b
-
None
-
Query Tool
-
Queries
-
i2b2 Web Client
-
PCORI, SCILHS, SHRINE
-
All databases
-
All Web Browsers
-
Verified the Query Tool times out in the specified time frame and the appropriate timeout message is displayed to the user.
Description
If a query is taking longer than the defined 180 seconds to run, the user should be presented with a message saying the query has timed out and will continue to run in the background.
The problem in the PCORI Web Clients (SHRINE and PHS) is the timeout message is not displaying to the user. The client will continue to display "Running" in the Query Status panel and the timer will continue to advance.
The only way to "free up" the client is to log out and log back in. Provided the query has finished running in the background, the user can drag the query from Previous Queries to the Query Tool to see the results of the query.
WARNING:
Whatever you do, DO NOT CANCEL the query because even if the query has finished running in the background the Query will be "cancelled" and the DELETE_FLAG will be set to Y. This means the query will not be visible to the user in the Previous Queries.
The problem in the PCORI Web Clients (SHRINE and PHS) is the timeout message is not displaying to the user. The client will continue to display "Running" in the Query Status panel and the timer will continue to advance.
The only way to "free up" the client is to log out and log back in. Provided the query has finished running in the background, the user can drag the query from Previous Queries to the Query Tool to see the results of the query.
WARNING:
Whatever you do, DO NOT CANCEL the query because even if the query has finished running in the background the Query will be "cancelled" and the DELETE_FLAG will be set to Y. This means the query will not be visible to the user in the Previous Queries.
Attachments
Activity
This issue was originally reported by the PCORI team and is entered in their JIRA as PCORI-14.
Donahoe, Janice M added a comment - 27/May/16 9:09 AM
The following error is occurring at the point where the timeout message should appear to the user.
CRC_ctrlr_QryStatus.js:570 Uncaught TypeError: Cannot read property 'firstChild' of undefined
callbackQueryDef.callback @ CRC_ctrlr_QryStatus.js:570
retCommObj._defaultCallbackOK @ i2b2_cell_communicator.js:355
success @ i2b2_cell_communicator.js:204
handleTransactionResponse @ utilities.js:17
(anonymous function) @ utilities.js:17
Mendis, Michael E. added a comment - 1/Jun/16 12:09 PM
Found issue and going to be part of 1.7.07c which should be released by end of week