[ http://issues.apache.org/jira/browse/DERBY-1272?page=comments#action_12419838 ]
Andrew McIntyre commented on DERBY-1272: ---------------------------------------- This passes on my Mac OS X box, with either sane or insane. About which, btw, I'm very confused. On Windows XP, it fails with the error you described. Based on the output, the failure is actually in errorStream/VombatusUrsinusHirsitus-err-4.log, and the log there provides a stack trace with the actual SecurityException. So, an excellent choice of test for this, although I'm a bit confused with the test results I have currently. Clearly some more investigation is required. Thanks for trying out the patch, Kathey. I think this has exposed a security manager issue that needs to be cleaned up inside of sysinfo. > Change sysinfo to print to error log (derby.log) on boot of derby if > derby.stream.error.logSeverityLevel=0 > ----------------------------------------------------------------------------------------------------------- > > Key: DERBY-1272 > URL: http://issues.apache.org/jira/browse/DERBY-1272 > Project: Derby > Type: Improvement > Components: Tools > Versions: 10.2.0.0, 10.1.2.1, 10.1.3.0 > Reporter: Kathey Marsden > Priority: Minor > Attachments: derby-1272-pre.diff, derby-1272-pre2.diff, > derby-1272-pre3.diff, derby-1272-v4.diff > > It is often very difficult to collect correct sysinfo output from user > environments because sysinfo run from the commandline does not have the same > classpath as the jvm that started Derby or Derby was loaded with a custom > classloader. > It would be very helpful in assisting users in diagnosing their issues if > sysinfo dumped to the error log if derby.stream.error.logSeverityLevel=0 or > even by default. -- 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
