Rick Hillegas created DERBY-5757:
------------------------------------
Summary: Attempting to boot Derby with a bad authentication
provider creates a zombie Derby which can only be killed by shutting down the
VM.
Key: DERBY-5757
URL: https://issues.apache.org/jira/browse/DERBY-5757
Project: Derby
Issue Type: Bug
Components: Miscellaneous
Affects Versions: 10.9.0.0
Reporter: Rick Hillegas
Priority: Minor
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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
