Derby
  1. Derby
  2. DERBY-5029

getParentLogger() won't work after the engine has been shut down once

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.7.1.1
    • Fix Version/s: 10.8.1.2
    • Component/s: JDBC
    • Labels:
      None
    • Environment:
      Windows 7 64 bits
    • Issue & fix info:
      Patch Available

      Description

      Plans for JDBC 4.1 implementation are dependent on Autoloader40 being loaded after shutdown so that the getParentLogger() function will work. The attached program ww.java provided by rick in discussions on DERBY-2905 show that AutoloadedDriver would get loaded instead. This will prevent getParentLogger() from working once implemented.

      1. DERBY-5029-1.diff
        4 kB
        Lily Wei
      2. DERBY-5029-1.diff
        4 kB
        Lily Wei
      3. DERBY-5029-1.diff
        4 kB
        Lily Wei

        Issue Links

          Activity

          Gavin made changes -
          Workflow jira [ 12552773 ] Default workflow, editable Closed status [ 12798991 ]
          Knut Anders Hatlen made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Rick Hillegas made changes -
          Fix Version/s 10.8.1.2 [ 12316362 ]
          Fix Version/s 10.8.1.1 [ 12316356 ]
          Rick Hillegas made changes -
          Fix Version/s 10.8.1.1 [ 12316356 ]
          Fix Version/s 10.8.1.0 [ 12315561 ]
          Knut Anders Hatlen made changes -
          Link This issue is duplicated by DERBY-5027 [ DERBY-5027 ]
          Lily Wei made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Issue & fix info [Patch Available]
          Assignee Lily Wei [ lilywei ]
          Resolution Fixed [ 1 ]
          Lily Wei made changes -
          Attachment DERBY-5029-1.diff [ 12470913 ]
          Lily Wei made changes -
          Attachment DERBY-5029-1.diff [ 12470907 ]
          Lily Wei made changes -
          Attachment DERBY-5029-1.diff [ 12470901 ]
          Lily Wei made changes -
          Description The getParentLogger() function will not work after engine has been shutdown once. Plans for JDBC 4.1 implementation are dependent on Autoloader40 being loaded after shutdown so that the getParentLogger() function will work. The attached program ww.java provided by rick in discussions on DERBY-2905 show that AutoloadedDriver would get loaded instead. This will prevent getParentLogger() from working once implemented.
          Lily Wei made changes -
          Summary getParentLogger() wp work after the engine has been shut down once getParentLogger() won't work after the engine has been shut down once
          Description The getParentLogger() function does not work after engine has been shutdown once. The getParentLogger() function will not work after engine has been shutdown once.
          Lily Wei made changes -
          Field Original Value New Value
          Summary getParentLogger() doesn't work after the engine has been shut down once getParentLogger() wp work after the engine has been shut down once
          Lily Wei created issue -

            People

            • Assignee:
              Lily Wei
              Reporter:
              Lily Wei
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development