Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 19 Jun 2012 20:00:43 +0000 (UTC)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <1790015758.31216.1340136043190.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1675905150.50625.1336674173281.JavaMail.tomcat@hel.zones.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.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mamta A. Satoor commented on DERBY-5757:
----------------------------------------

Would shutting Derby internally when a bad authentication class is found would be an acceptable solution? I have no idea what that solution will involve but I was just curious what we think would be some ideas on handling such a case.
                
> 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