[ http://issues.apache.org/jira/browse/DERBY-616?page=comments#action_12366041 ]
Myrna van Lunteren commented on DERBY-616: ------------------------------------------ DERBY-943 is most likely related to this issue. See also the mail archives: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200602.mbox/[EMAIL PROTECTED] and: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200602.mbox/[EMAIL PROTECTED] So, For 'fixing' the nightly failure issue of DERBY-943, I will add the read, write, delete java.io.FilePermission to derby_tests.policy for the syscatdb/tmp dir (and under) in the derbynet.jar section. When this (DERBY-616) bug gets fixed, that section should also be taken out, and syscat.sql should be confirmed to work successfully with ibm142 jvm. > create index can fail under the SecurityManager when trying to access files > in the tmp folder of a database > ----------------------------------------------------------------------------------------------------------- > > Key: DERBY-616 > URL: http://issues.apache.org/jira/browse/DERBY-616 > Project: Derby > Type: Bug > Components: Store > Versions: 10.0.2.1, 10.1.1.0, 10.2.0.0 > Reporter: Daniel John Debrunner > Priority: Critical > > Seen in tests lang/wisconsin.sql and jdbcapi/maxfieldsize.java when running > with the network server and the new security policy file that grants > permisions on a per-jar basis. Unless permission is given to the network > serve code (since it is in the stack) to access temp files in the database > the test will fail. > permission java.io.FilePermission > "${derby.system.home}${/}wombat${/}tmp${/}-", "read, write, delete"; > Most likely the temp files are being accessed in without a privileged block. > Easy to reproduce once the new policy file changes are checked in (see > http://wiki.apache.org/db-derby/SecurityManagerTesting) by removing the > permission in the derby_tests.policy file and running these tests using the > jar files. -- 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
