Sysinfo should print a better message when it gets Security Exceptions accessing classpath info when run under security manager

• Key: DERBY-1273
• Type: Improvement
• Status: Open
• Priority: Minor
• Assignee: Unassigned
• Reporter: Kathey Marsden
• Component/s: Tools
• Affects Version/s: 10.2.1.6

Description

If sysinfo does not have getProtectionDomain privileges it cannot get some information during classpath handling.
When this occurs it prints Java Security Exceptions in the output e.g.

JRE - JDBC: J2SE 1.4.2 - JDBC 3.0
[C:\bryan\src\derby\main\trunk\jars\sane\derby.jar] 10.2.0.0 alpha - (398049M)
[C:\bryan\src\derby\main\trunk\jars\sane\derbytools.jar] 10.2.0.0 alpha - (398049M)
[C:\bryan\src\derby\main\trunk\jars\sane\derbynet.jar] 10.2.0.0 alpha - (398049M)
[C:\bryan\src\derby\main\trunk\jars\sane\derbyclient.jar] 10.2.0.0 alpha - (398049M)
[Unable to access Protection Domain or Code Source for class class com.ibm.db2.jcc.DB2Driver: access denied (java.lang.RuntimePermission getProtectionDomain)] 2.4 - (17)
[C:\bryan\src\derby\main\trunk\jars\sane\db2jcc_license_c.jar] 2.4 - (17)
[Java Security Exception: access denied (java.io.FilePermission c:\bryan\src\derby\main\trunk\tools\java\jakarta-oro-2.0.8.jar read)]
[Java Security Exception: access denied (java.io.FilePermission c:\bryan\src\derby\main\trunk\tools\java\junit.jar read)]

See DERBY-1229 notes.html for a complete explanation of the output.

I am actually not sure what information is actually missing from sysinfo in this case but I think it would be better if sysinfo just printed the classpath and then printed a generic warning with the information that it was not able to report rather than printing the Security exceptions explicitly.

This would be especially helpful for NetworkServerControl sysinfo because users are always encouraged to run network server in security manager.