[ http://issues.apache.org/jira/browse/DERBY-623?page=all ]

Kristian Waagan updated DERBY-623:
----------------------------------

    Attachment: DERBY-623-1b.diff
                DERBY-623-1b.stat

Dan, I see your point now! I do still mean we need another Jira though, to 
track cleaning up BaseMonitor (primarily method 'runWithState').

'DERBY-623-1b.diff' is a reduced patch, only addressing reading two specific 
system properties in privileged blocks and updating the test policy file 
accordingly.
Patch 'DERBY-623-1a.diff' is now deprecated.
Tests run on Solaris10, Sun 1.5:
derbyall - insane - jars:  derbynet/runtimeinfo.java, jdbcapi/Stream.java and 
jdbcapi/SURTest.junit failed.
derbyall - sane - jars: OK! (stress.multi failed)
derbyall - sane - classes: NSinSameJVM failed.

I don't think the errors are caused by the changes, but if anyone else thinks 
so, speak up!


> Derby monitor accesses two system properties without using a privileged block 
> when built sane=true
> --------------------------------------------------------------------------------------------------
>
>          Key: DERBY-623
>          URL: http://issues.apache.org/jira/browse/DERBY-623
>      Project: Derby
>         Type: Bug
>   Components: Services
>     Versions: 10.2.0.0
>     Reporter: Daniel John Debrunner
>     Assignee: Kristian Waagan
>     Priority: Minor
>  Attachments: DERBY-623-1a.diff, DERBY-623-1a.stat, DERBY-623-1b.diff, 
> DERBY-623-1b.stat, DERBY-623-2b-javadoc.diff, DERBY-623-2b-javadoc.stat
>
> When built with sane=true and testing with the jars these permissions are 
> required to be granted all the way up the stack, currently this means for the 
> tests granting them to the network server jar.
>   permission java.util.PropertyPermission "derby.monitor.verbose", "read";
>   permission java.util.PropertyPermission "derby.debug.*", "read";
> The engine contains code to read system properties using privileged blocks, 
> this should be used by the monitor.

-- 
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

Reply via email to