Derby
  1. Derby
  2. DERBY-5152

Shutting down db, information that the thread received an interrupt will not be restored to thread's interrupt flag

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 10.8.1.2
    • Fix Version/s: 10.8.1.2
    • Component/s: None
    • Labels:
      None

      Description

      When a thread receives an interrupt Derby detects this, it will reset the thread's flag and save the fact in its lcc (LanguageConnectionContext), if available. If not (e.g. during boot) it will save the information in a thread local variable. For performance reasons, we use the lcc when available. However, when shutting down the database, the lcc goers away, and when the JDBC call returns to the application, the thread's interrupt flag will not be reinstated as per our specification. This is because the lcc dies before we do the restoring (under shutdown). So, the information that the thread was interrupted is lost with the lcc going away. A possible solution is to move the flag over to the thread local variable when the lcc is popped, so that the restore code will find it.

      1. derby-5152-b.stat
        0.3 kB
        Dag H. Wanvik
      2. derby-5152-b.diff
        4 kB
        Dag H. Wanvik
      3. derby-5152.stat
        0.3 kB
        Dag H. Wanvik
      4. derby-5152.diff
        4 kB
        Dag H. Wanvik

        Issue Links

          Activity

          Dag H. Wanvik created issue -
          Dag H. Wanvik made changes -
          Field Original Value New Value
          Link This issue is part of DERBY-4741 [ DERBY-4741 ]
          Dag H. Wanvik made changes -
          Assignee Dag H. Wanvik [ dagw ]
          Dag H. Wanvik made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          Dag H. Wanvik made changes -
          Attachment derby-5152.diff [ 12474628 ]
          Attachment derby-5152.stat [ 12474629 ]
          Dag H. Wanvik made changes -
          Issue & fix info [Patch Available]
          Dag H. Wanvik made changes -
          Attachment derby-5152-b.diff [ 12474825 ]
          Attachment derby-5152-b.stat [ 12474826 ]
          Dag H. Wanvik made changes -
          Attachment derby-5152-b.diff [ 12474825 ]
          Dag H. Wanvik made changes -
          Attachment derby-5152-b.diff [ 12474827 ]
          Dag H. Wanvik made changes -
          Attachment derby-5152-b.stat [ 12474826 ]
          Dag H. Wanvik made changes -
          Attachment derby-5152-b.stat [ 12474828 ]
          Dag H. Wanvik made changes -
          Status In Progress [ 3 ] Closed [ 6 ]
          Issue & fix info [Patch Available]
          Resolution Fixed [ 1 ]
          Dag H. Wanvik made changes -
          Resolution Fixed [ 1 ]
          Status Closed [ 6 ] Reopened [ 4 ]
          Dag H. Wanvik made changes -
          Fix Version/s 10.8.0.0 [ 12315561 ]
          Dag H. Wanvik made changes -
          Status Reopened [ 4 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]
          Rick Hillegas made changes -
          Affects Version/s 10.8.1.1 [ 12316356 ]
          Affects Version/s 10.8.1.0 [ 12315561 ]
          Fix Version/s 10.8.1.1 [ 12316356 ]
          Fix Version/s 10.8.1.0 [ 12315561 ]
          Rick Hillegas made changes -
          Affects Version/s 10.8.1.2 [ 12316362 ]
          Affects Version/s 10.8.1.1 [ 12316356 ]
          Fix Version/s 10.8.1.2 [ 12316362 ]
          Fix Version/s 10.8.1.1 [ 12316356 ]
          Gavin made changes -
          Workflow jira [ 12608641 ] Default workflow, editable Closed status [ 12801041 ]

            People

            • Assignee:
              Dag H. Wanvik
              Reporter:
              Dag H. Wanvik
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development