Derby
  1. Derby
  2. DERBY-5085

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

    Details

    • Urgency:
      Blocker
    • Issue & fix info:
      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.

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

        Issue Links

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development