You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2015/10/16 19:33:05 UTC
[jira] [Commented] (DERBY-6334) Test harness security policy
prevents running DatabaseClassLoadingTest twice
[ https://issues.apache.org/jira/browse/DERBY-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961066#comment-14961066 ]
Kathey Marsden commented on DERBY-6334:
---------------------------------------
This seems to be resolved. The test runs twice in a row fine for me. It may be related to this fix:
r1582655 | kahatlen | 2014-03-28 02:44:37 -0700 (Fri, 28 Mar 2014) | 7 lines
DERBY-5615: Permission problems with classpath subsubprotocol
Wrap CPFile's privileged operations in doPrivileged() so that
classpath databases can be accessed with a security manager.
Make more of the test cases in DatabaseClassLoadingTest and
NativeAuthenticationServiceTest run with a security manager.
Bryan, you ok with resolving this issue?
> Test harness security policy prevents running DatabaseClassLoadingTest twice
> ----------------------------------------------------------------------------
>
> Key: DERBY-6334
> URL: https://issues.apache.org/jira/browse/DERBY-6334
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.11.1.1
> Reporter: Bryan Pendleton
> Priority: Minor
>
> If I try to run DatabaseClassLoadingTest twice in a row, the second run
> immediately fails with a AccessControlException.
> To reproduce the problem:
> 1) cd to a fresh empty directory
> 2) java junit.textui.TestRunner org.apache.derbyTesting.functionTests.tests.lang.DatabaseClassLoadingTest
> (test will pass)
> 3) java junit.textui.TestRunner org.apache.derbyTesting.functionTests.tests.lang.DatabaseClassLoadingTest
> (test will fail with an AccessControlException)
> It's possible that this is due to a problem with the security policy that the
> test harness includes for running the unit tests?
> I'll include the stack trace in a comment to this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)