[
https://issues.apache.org/jira/browse/DERBY-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940456#comment-13940456
]
Knut Anders Hatlen commented on DERBY-6107:
-------------------------------------------
Here's one theory: The credentials database seems to be made available in the
context class loader of the test thread and is accessed using the classpath
subsubprotocol. When login timeout is enabled, getConnection() will delegate
the work to a thread from a pool. If the test runs separately, the thread pool
is probably empty, and a new thread is created in order to process the
getConnection() call. Presumably, this thread inherits the context class loader
of the current thread, and it therefore is able to access the credentials
database. However, if the thread pool is not empty when the test runs, the
getConnection() call is processed in a thread created by an earlier test, which
probably doesn't have the context class loader set up to access the credentials
database.
> Investigate why setting a login timeout causes
> NativeAuthenticationServiceTest to fail when run in a suite
> ----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6107
> URL: https://issues.apache.org/jira/browse/DERBY-6107
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.10.1.1
> Reporter: Rick Hillegas
>
> See DERBY-6094 for the details of this problem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
