Uploaded image for project: 'i2b2 Core Software'
  1. i2b2 Core Software
  2. CORE-243

Queries do not stop running when they time out of the large queue

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.7.08
    • 1.7.08a
    • CRC Cell
    • None
    • Queries
    • i2b2 Core
    • All databases
    • All Web Browsers
    • Fixed by Mike Mendis and is included in Release 1.7.08a
    • Hide
      In summary, the testing involved verifying queries were stopping and the thread was ending correctly when a query times out of any queue.

      NOTE: This issue was tested in conjunction with CORE-236, CORE-241, CORE-242 and CORE-244. The attached file is the full checklist of what was tested for release 1.7.08a.
      Show
      In summary, the testing involved verifying queries were stopping and the thread was ending correctly when a query times out of any queue. NOTE: This issue was tested in conjunction with CORE-236 , CORE-241 , CORE-242 and CORE-244 . The attached file is the full checklist of what was tested for release 1.7.08a.
    • edu.harvard.i2b2.crc

    Description

      When a query times out of the large queue the statuses are updated to reflect that it has timed out and is no longer running. However it appears the thread is not ending correctly and the query is continuing to run. Since the query has timed out of the large queue, the next query in the queue will run. This has the potential of numerous queries running for an extensive amount of time. It is not clear what affect this would have on space issues and response time for other queries.




      Attachments

        Issue Links

          clone of

          Bug - A problem which impairs or prevents the functions of the product. CORE-236 Error returned when query times out

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. CORE-242 Queries are stuck in queue when previous query results in an error

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. CORE-244 Statuses are not updated when query times out or an error occurs

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            jmd86 Janice Donahoe created issue -
            jmd86 Janice Donahoe made changes -
            Field Original Value New Value
            Link This issue clone of CORE-242 [ CORE-242 ]
            jmd86 Janice Donahoe made changes -
            Developer Notes Fixed by Mike Mendis and is included in Release 1.7.08a
            Server Plug-in/s Modified edu.harvard.i2b2.crc [ 10114 ]
            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.
            		In summary, the testing involved verifying queries were stopping and the thread was ending correctly when a query times out of any queue.

            NOTE: This issue was tested in conjunction with CORE-236, CORE-241, CORE-242 and CORE-244. The attached file is the full checklist of what was tested for release 1.7.08a.
            Description 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.



            		When a query times out of the large queue the statuses are updated to reflect that it has timed out and is no longer running. However it appears the thread is not ending correctly and the query is continuing to run. Since the query has timed out of the large queue, the next query in the queue will run. This has the potential of numerous queries running for an extensive amount of time. It is not clear what affect this would have on space issues and response time for other queries.




            Summary Queries do not stop running when timed out of the large queue Queries do not stop running when they time out of the large queue
            jmd86 Janice Donahoe made changes -
            Link This issue clone of CORE-244 [ CORE-244 ]
            jmd86 Janice Donahoe made changes -
            Link This issue clone of CORE-236 [ CORE-236 ]
            jmd86 Janice Donahoe made changes -
            i2b2 Feature/s Queries [ 10081 ]
            Status New [ 10000 ] Open [ 1 ]
            jmd86 Janice Donahoe made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            jmd86 Janice Donahoe made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Resolved [ 5 ]
            jmd86 Janice Donahoe added a comment -
            The change for this issue was included in the 1.7.08a release.
            jmd86 Janice Donahoe added a comment - The change for this issue was included in the 1.7.08a release.
            jmd86 Janice Donahoe made changes -
            Status Resolved [ 5 ] Closed [ 6 ]

            People

              jmd86 Janice Donahoe
              jmd86 Janice Donahoe
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: