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

Attempting to boot Derby with a bad authentication provider creates a zombie Derby which can only be killed by shutting down the VM.

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.9.1.0
    • Fix Version/s: None
    • Component/s: Miscellaneous
    • Urgency:
      Normal
    • Issue & fix info:
      Repro attached

      Description

      If you set the following system properties and try to connect to Derby, this will half-boot Derby. You will not be able to get a connection because no valid authentication service can be found. In addition, you won't be able to bring down the half-booted Derby because that also requires getting a valid authentication service. This is true even if you remove the properties from the system via System.getProperties().remove(). The bad property settings are stuck inside the half-booted Derby, preventing it from installing a usable authentication service:

      derby.connection.requireAuthentication=true
      derby.authentication.provider=bad:class

        Attachments

        1. Derby_5757.java
          1 kB
          Rick Hillegas

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              rhillegas Rick Hillegas
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: