db-derby-dev mailing list archives

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

     [ https://issues.apache.org/jira/browse/DERBY-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Hillegas updated DERBY-5607:
---------------------------------

    Attachment: derby-5607-01-aa-userInternalDriver.diff

Attaching derby-5607-01-aa-useInternalDriver.diff. This patch changes the way that the NATIVE
authentication service opens a connection to Credentials DB when system-wide privileges need
to be authenticated. Previously, the service called in through the Derby DataSources, which
in turn called through the JDBC api. The deadlock occurred in that call through the JDBC api
which happened inside the user's original JDBC call. That approach is replaced: now the NATIVE
authentication service opens a connection to the Credentials DB using Derby's own InternalDriver,
skipping the need for a nested call through JDBC.

With this patch, the NASTHang test case now runs correctly on Java 5.

I have run the NativeAuthenticationServiceTest successfully on the following platforms:

1) Java 6 on Mac OSX.

2) Java 5 on Linux.

3) CDC/FP 1.1 on OJEC.

On the strength of those successful runs, I have committed this patch at subversion revision
1242105. Let's see if this fixes the nightly tests on the other Java 5 platforms.


Touches the following file:

M       java/engine/org/apache/derby/impl/jdbc/authentication/NativeAuthenticationServiceImpl.java

                
> 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: 10.9.0.0
>            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

        

Mime
View raw message