8008793: SecurityManager.checkXXX behavior not specified for methods that check AWTPermission and AWT not present

Sean Mullan sean.mullan at oracle.com
Mon Feb 25 16:39:56 UTC 2013


On 02/25/13 11:32, Alan Bateman wrote:
> On 25/02/2013 16:04, Sean Mullan wrote:
>>
>> But there can be only one SM, so it could potentially affect other
>> tests in different threads that depend on an SM. (If 2 tests that set
>> their own SM ran in the same VM, potential issues would result, right?).
> Tests run sequentially in the same VM (never concurrently). At the end
> of each test then jtreg will attempt to restore the security manager if
> set by the test. So I think we are okay here, it's not an issue in my
> test runs and this test is already using a security manager.

Ah I see. However, the jtreg FAQ [1] still advises running these in its 
own VM. Might want to check to see what Jonathan Gibbons says.

--Sean

[1] http://openjdk.java.net/jtreg/faq.html#question4.17




More information about the security-dev mailing list