[
https://issues.apache.org/jira/browse/DERBY-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5607:
---------------------------------
Attachment: NASTHang.java
Attaching NASTHang.java. This short program demonstrates the problem. Make sure
that you compile this program at bytecode level 1.5 or earlier so that you can
run it on Java 5.
> 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
> Attachments: NASTHang.java
>
>
> 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
