Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-5085

After specifying deregister=false on the engine shutdown URL, Derby forgets that the default behavior is deregister=true

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Blocker
    • Patch Available, Repro attached

    Description

      If you shutdown the engine specifying deregister=false, then get a new connection, then shutdown the engine again without specifying any value for the deregister attribute, Derby acts as though you specified deregister=false again. I will attach a test program which shows this problem.

      Attachments

        1. DERBY-5085_1.diff
          0.6 kB
          Lily Wei
        2. y.java
          2 kB
          Richard N. Hillegas

        Issue Links

        is part of

        Bug - A problem which impairs or prevents the functions of the product. DERBY-2905 Shutting down embedded Derby does not remove all code, the AutoloadDriver is left registered in the DriverManager.

        • Major - Major loss of function.
        • Closed

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            lilywei Lily Wei
            rhillegas Richard N. Hillegas
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment