Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.7.09c
    • None
    • None

    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.

      Attachments

        Activity

          mem61 Mike Mendis created issue -
          mem61 Mike Mendis made changes -
          Field Original Value New Value
          Status New [ 10000 ] Open [ 1 ]
          mem61 Mike Mendis made changes -
          Assignee Mike Mendis [ mem61 ]
          mem61 Mike Mendis made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          mem61 Mike Mendis made changes -
          Assignee Mike Mendis [ mem61 ] Janice Donahoe [ jmd86 ]
          Status In Progress [ 3 ] Ready to Test [ 10001 ]
          jmd86 Janice Donahoe made changes -
          Fix Version/s 1.7.09c [ 10800 ]
          jmd86 Janice Donahoe made changes -
          Status Ready to Test [ 10001 ] Testing [ 10002 ]
          jmd86 Janice Donahoe made changes -
          Summary webclient failed to cancel query after informing obfuscated user he is locked out Webclient failed to cancel query after informing obfuscated user he is locked out
          jmd86 Janice Donahoe made changes -
          Description RUnning a query as a locked out user, they cant cancel it. When an obfuscated exceeds the allowed number of times they can repeat a query they will be "locked out" from running another query. When they receive the message telling them they have been locked out, the system should cancel the query they are trying to run. However, when they click on OK the Web Client continues to run the query.

          The resolution is to have the Web Client "cancel" the query when the lockout message is received from the CRC.


          GIT COMMIT 3ff17f73549eff306ead0fafdfb780f09ef018f0
          jmd86 Janice Donahoe added a comment - - edited
          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.
          jmd86 Janice Donahoe added a comment - - edited 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.
          jmd86 Janice Donahoe made changes -
          Resolution Fixed [ 1 ]
          Status Testing [ 10002 ] Resolved [ 5 ]
          jmd86 Janice Donahoe made changes -
          Summary Webclient failed to cancel query after informing obfuscated user he is locked out Web Client doesn't cancel query when user receives lockout message
          jmd86 Janice Donahoe made changes -
          Resolution Fixed [ 1 ]
          Status Resolved [ 5 ] Reopened [ 4 ]
          jmd86 Janice Donahoe made changes -
          Status Reopened [ 4 ] In Progress [ 3 ]
          jmd86 Janice Donahoe made changes -
          Assignee Janice Donahoe [ jmd86 ] Mike Mendis [ mem61 ]
          jmd86 Janice Donahoe made changes -
          jmd86 Janice Donahoe made changes -
          Attachment obfscUser-lockOut-qryError.png [ 10933 ]
          jmd86 Janice Donahoe made changes -
          Link This issue clone of WEBCLIENT-224 [ WEBCLIENT-224 ]
          jmd86 Janice Donahoe made changes -
          Link This issue clone of WEBCLIENT-224 [ WEBCLIENT-224 ]
          mem61 Mike Mendis made changes -
          Description When an obfuscated exceeds the allowed number of times they can repeat a query they will be "locked out" from running another query. When they receive the message telling them they have been locked out, the system should cancel the query they are trying to run. However, when they click on OK the Web Client continues to run the query.

          The resolution is to have the Web Client "cancel" the query when the lockout message is received from the CRC.


          GIT COMMIT 3ff17f73549eff306ead0fafdfb780f09ef018f0
          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.
          Summary Web Client doesn't cancel query when user receives lockout message Web Client possible null pointer
          This was fixed and released in version 1.7.09c
          jmd86 Janice Donahoe added a comment - This was fixed and released in version 1.7.09c
          jmd86 Janice Donahoe made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Resolved [ 5 ]
          jmd86 Janice Donahoe made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rm302 Reeta Metta made changes -
          Attachment dtconst_ptst.PNG [ 11031 ]
          rm302 Reeta Metta made changes -
          Attachment dtconst_ptst.PNG [ 11031 ]

          People

            mem61 Mike Mendis
            mem61 Mike Mendis
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: