[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.

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.9.1.0
• Component/s: Miscellaneous
• Labels: derby_triage10_10
• Urgency: Normal
• Issue & fix info: Repro attached
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 10/May/12 18:22
• Updated: 27/Sep/12 19:36

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