Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Won't Fix
-
10.1.2.1, 10.1.3.1, 10.2.1.6
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- incorporates
-
DERBY-4715 Write jvm information and path of derby.jar to derby.log
- Closed
- is related to
-
DERBY-3188 'Failure in loading T2 native library db2jcct2' in lang/triggerGeneral.sql
- Closed
-
DERBY-4441 Change sysinfo to print out more specific JVM information
- Closed
- relates to
-
DERBY-1487 Use of getCanonicalPath() in sysinfo causes a SecurityException
- Open
-
DERBY-5240 Log Operating system information to derby.log on boot
- Closed