[CORE-242] Queries are stuck in queue when previous query results in an error Created: 23/Nov/16  Updated: 09/Dec/16  Resolved: 23/Nov/16

Status: Closed
Project: i2b2 Core Software
Component/s: CRC Cell
Affects Version/s: 1.7.08
Fix Version/s: 1.7.08a

Type: Bug Priority: Major
Reporter: Janice Donahoe Assignee: Janice Donahoe
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PDF File Release 1-7-08a Checklist.pdf    
Issue Links:
clone of CORE-236 Error returned when query times out Closed
clone of CORE-244 Statuses are not updated when query t... Closed
clone of CORE-243 Queries do not stop running when they... Closed
Rank: 0|i00387:
Sprint: Release 1.7.08a Sprint
i2b2 Feature/s:
i2b2 Sponsored Project/s:
i2b2 Core
Affects Database/s:
All databases
Affects Web Browser/s:
All Web Browsers
Developer Notes: Fixed by Mike Mendis and is included in Release 1.7.08a
Testing Notes: In summary, the testing involved verifying the next query in a queue would run when a query generates an error.

NOTE: This issue was tested in conjunction with CORE-236. The attached file is the full checklist of what was tested for release 1.7.08a.
Server Plug-in/s Modified:

When a query errors out in the medium or large queue it is locking up or dropping the queue thread so no other queries are being run. The only way to free up the queue is to restart WildFly.

What Should Happen
If a query generates an error while running in any of the queues the following should occur.

* The statuses are updated in the QT_QUERY_INSTANCE and QT_QUERY_RESULT_INSTANCE tables.
* The END_DATE in the tables is updated to indicate the query is done running.
* The queue should be free to begin running the next query.

Comment by Janice Donahoe [ 09/Dec/16 ]
The change for this issue was included in the 1.7.08a release.
Generated at Wed May 25 20:27:44 UTC 2022 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.