db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (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 13:14:44 GMT

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

Rick Hillegas commented on DERBY-5757:
--------------------------------------

Hi Mamta: The bug might be addressed by returning to an initial position if a system-wide
service (like system-wide authentication) fails to boot. Initial position means that service
startup re-reads the system properties. Shutting down Derby might return Derby to initial
position, depending on where you jump into the shutdown code. As the repro shows, you can't
shutdown Derby from the JDBC level after the system-wide authentication service falls over.

Hi Knut: If initial position also means that zombie threads are destroyed, then some part
of DERBY-594 might be addressed. I haven't looked into that bug though. Thanks.
                
> 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