db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5607) Deadlock in Java 5 VM when using NATIVE authentication with a client running in the same VM as the server
Date Fri, 17 Feb 2012 19:01:59 GMT

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

Rick Hillegas commented on DERBY-5607:

Hi Kathey,

That might make sense and might eliminate other possible deadlocks in the VM. On the other
hand, Derby bootstrapping has proven to be very brittle and we would want to think about this
carefully. Unless we have evidence that there is another deadlock in there, I would advice
caution. Thanks.
> Deadlock in Java 5 VM when using NATIVE authentication with a client running in the same
VM as the server
> ---------------------------------------------------------------------------------------------------------
>                 Key: DERBY-5607
>                 URL: https://issues.apache.org/jira/browse/DERBY-5607
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client, Network Server, Services
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: NASTHang.java, derby-5607-01-aa-userInternalDriver.diff
> A deadlock in the Java 5 VM hangs connection attempts if you are using NATIVE authentication
with a client which runs in the same VM as the server. I will attach a test case which demonstrates
this. This bug is implicated in the failures being discussed on https://issues.apache.org/jira/browse/DERBY-5601
and was disclosed by the discussion on this email thread: http://old.nabble.com/-URGENT--Critical-test-situation-on-trunk-to33259629.html#a33259629
> The bug arises when NativeAuthenticationServiceImpl attempts a nested connection to the
Credentials database during database creation. The nested connection is attempted in order
to dertermine whether the user has system-wide privilege to create databases.

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


View raw message