Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9390010982 for ; Mon, 2 Dec 2013 17:13:52 +0000 (UTC) Received: (qmail 8852 invoked by uid 500); 2 Dec 2013 17:05:39 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 795 invoked by uid 500); 2 Dec 2013 16:57:38 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 97854 invoked by uid 99); 2 Dec 2013 16:17:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Dec 2013 16:17:42 +0000 Date: Mon, 2 Dec 2013 16:17:41 +0000 (UTC) From: "Myrna van Lunteren (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DERBY-6352) Access denied ("java.lang.RuntimePermission" "modifyThread") in store.RecoveryAfterBackup test MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836645#comment-13836645 ] Myrna van Lunteren commented on DERBY-6352: ------------------------------------------- Just to note, that I also saw this in recent test runs against older branches (10.6 and 10.3) with ibm 1.6. > Access denied ("java.lang.RuntimePermission" "modifyThread") in store.RecoveryAfterBackup test > ---------------------------------------------------------------------------------------------- > > Key: DERBY-6352 > URL: https://issues.apache.org/jira/browse/DERBY-6352 > Project: Derby > Issue Type: Bug > Components: Test > Affects Versions: 10.10.1.1 > Environment: IBM java 7 Derby version 10.10.1.2 - (1494414) > Reporter: Kathey Marsden > Attachments: DERBY-6352_trunk.diff, DERBY-6352_trunk2.diff > > > I got a report of the following intermittent (6/60) exception in store.RecoveryAfterBackupTest. > Exception in thread "main" java.security.AccessControlException: Access denied ("java.lang.RuntimePermission" "modifyThread") > at java.security.AccessController.throwACE(AccessController.java:100) > at java.security.AccessController.checkPermission(AccessController.java:174) > at java.lang.SecurityManager.checkPermission(SecurityManager.java:549) > at java.lang.SecurityManager.checkAccess(SecurityManager.java:676) > at java.lang.Thread.checkAccess(Thread.java:459) > at java.lang.Thread.interrupt(Thread.java:588) > at org.apache.derby.iapi.services.context.ContextService$1.run(Unknown Source) > at java.security.AccessController.doPrivileged(AccessController.java:274) > at org.apache.derby.iapi.services.context.ContextService.notifyAllActiveThreads(Unknown Source) > at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(Unknown Source) > at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) > at org.apache.derby.jdbc.Driver20.connect(Unknown Source) > at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source) > at java.sql.DriverManager.getConnection(DriverManager.java:571) > at java.sql.DriverManager.getConnection(DriverManager.java:233) > at org.apache.derbyTesting.functionTests.util.TestUtil.getConnection(TestUtil.java:836) > at org.apache.derbyTesting.functionTests.tests.store.RecoveryAfterBackup.main(RecoveryAfterBackup.java:82) > modifyThread is a necessary permission if interrupting a thread other than the current thread but is not in our policy file for derby.jar. > The relevant code in ContextService is: > for (ContextManager cm : allContexts) { > Thread active = cm.activeThread; > if (active == me) > continue; > if (active == null) > continue; > final Thread fActive = active; > if (cm.setInterrupted(c)) > { > AccessController.doPrivileged( > new PrivilegedAction() { > public Void run() { > fActive.interrupt(); > return null; > } > }); > } > > I am not sure why this has never come up before. Are we expecting in this context that fActive is the current thread? > -- This message was sent by Atlassian JIRA (v6.1#6144)