[DERBY-5607] Deadlock in Java 5 VM when using NATIVE authentication with a client running in the same VM as the server

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 10.9.1.0
• Fix Version/s: 10.9.1.0
• Component/s: Network Client, Network Server, Services
• Labels: derby_backport_reject_10_8 derby_triage10_9
• Urgency: Normal
• Issue & fix info: Patch Available, Repro attached
• Bug behavior facts: Regression Test Failure
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 08/Feb/12 19:32
• Updated: 05/Jul/13 12:42
• Resolved: 14/Jun/13 16:50

Description

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.

Issue Links

• is part of: DERBY-5601 Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
• is part of: DERBY-866 Derby User Management Enhancements