db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (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.
Date Wed, 20 Jun 2012 11:54:43 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397438#comment-13397438
] 

Knut Anders Hatlen commented on DERBY-5757:
-------------------------------------------

I'm wondering if this issue is somehow related to DERBY-594.
                
> 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.1.0
>            Reporter: Rick Hillegas
>            Priority: Minor
>         Attachments: Derby_5757.java
>
>
> 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

        

Mime
View raw message