[ http://issues.apache.org/jira/browse/DERBY-623?page=comments#action_12368624 ]
Daniel John Debrunner commented on DERBY-623: --------------------------------------------- To reproduce this bug remove these permissions from derby_test.policy // BUG DERBY-623 - sane=true permission java.util.PropertyPermission "derby.monitor.verbose", "read"; permission java.util.PropertyPermission "derby.debug.*", "read"; Build with sane=true and then run derbyall with the sane jars. Probably will see the issue by only running derbynetclientmats and derbynetmats suites. > 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 > Priority: Minor > > 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
