[ http://issues.apache.org/jira/browse/DERBY-1272?page=all ]
Kathey Marsden updated DERBY-1272:
----------------------------------
Derby Info: (was: [Patch Available])
Unchecking patch available as more investigation is needed for the security
manager issue with sysinfo printing to derby.log. It may be a generic security
manager issue with sysinfo that requires another Jira entry.
Andrew are you actively working on this issue? I noticed it was unassigned. It
would be a huge supportability improvement for 10.2 if it can get in.
> 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
> Issue Type: Improvement
> Components: Tools
> Affects 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
