Mailing-List: contact harmony-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Message-ID: <14124923.1160045299587.JavaMail.root@brutus>
Date: Thu, 5 Oct 2006 03:48:19 -0700 (PDT)
From: "Elena Semukhina (JIRA)" <jira@apache.org>
To: harmony-commits@incubator.apache.org
Subject: [jira] Created: (HARMONY-1720) Classlib test
 org.apache.harmony.luni.tests.java.lang.ThreadTest.test_stop_subtest0 fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Classlib test org.apache.harmony.luni.tests.java.lang.ThreadTest.test_stop_subtest0 fails
-----------------------------------------------------------------------------------------

                 Key: HARMONY-1720
                 URL: http://issues.apache.org/jira/browse/HARMONY-1720
             Project: Harmony
          Issue Type: Bug
          Components: DRLVM
            Reporter: Elena Semukhina
            Priority: Critical


The test fails with the following assertion:

test_stop_subtest0(org.apache.harmony.luni.tests.java.lang.ThreadTest)junit.fework.AssertionFailedError: checkAccess called

The test does not expect that security manager's checkAccess() method is called when stopping a new thread which is not running yet.
I think it is a compatibility issue. 
The spec for Thread.stop() says:
If there is a security manager installed, its checkAccess method is called with this as its argument.

RI does not call this method for a thread which does not run, and this seems reasonable.
I suggest that drlvm would do the same.

NOTE: to reproduce the bug you should comment out ThreadTest.test_suspend() which hangs now. This issue is expected to be fixed with H-1519.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira