river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Firmstone <j...@zeus.net.au>
Subject An interesting concurrency bug
Date Wed, 04 Aug 2010 10:51:18 GMT

Got an interesting concurrency bug to solve, if you check out the latest 
revision, you can simulate this bug.  Go back to rev 981386, the bug 
isn't apparent.

Basically the changes are:


implies(ProtectionDomain, Permission)
    old version calls underlying basePolicy.implies() first, then 
    new version skips implies and calls basePolicy.getPermissions()

grant( Class ...)
   Changed to use AccessController.checkPermission()  instead of 
SecurityManager call of same name.

Only implies() is involved in this case.

The test in question:

The 7 tests that fail are related to PreferredPolicyProvider, no 
DynamicPolicy tests fail.

The reason the basedPolicy.implies() is no longer called is to remove 
the possiblity of a ConcurrentModificationException that would occur 
when an implies from a concurrent thread causes UnresolvedPermission's 
to become resolved, changing underlying state during an Enumeration.

Oh and the test passes when -Djava.security.debug=access:failure is used.

Test results attached.

I'll commit a changed to the build.xml file for qa, so you can run the 
test from the qa directory using ant run-tests



View raw message