[
https://issues.apache.org/jira/browse/DERBY-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden resolved DERBY-1272.
-----------------------------------
Resolution: Won't Fix
The solution of logging this information directly in derby.log without going
through the sysinfo tools code and without any special properties seems
preferable..
Functionality has been implemented except fro DERBY-5240 which is pending.
> Change sysinfo to print to error log (derby.log) on boot of derby if
> derby.stream.error.logSeverityLevel=0
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1272
> URL: https://issues.apache.org/jira/browse/DERBY-1272
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 10.1.2.1, 10.1.3.1, 10.2.1.6
> Reporter: Kathey Marsden
> Priority: Minor
> Attachments: DERBY-1272v5.diff, DERBY-1272v6.diff, DERBY-1272v6.stat,
> DERBY-1272v8.diff, 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
