[
https://issues.apache.org/jira/browse/DERBY-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778661#action_12778661
]
Myrna van Lunteren commented on DERBY-1272:
-------------------------------------------
I can understand how valuable it will be in a Tech Support situation of a
product that embeds another product that embeds another product that embeds
Derby to have sysinfo - with additional jvm data - show up in derby.log without
having to figure out where to set a property.
But I do think if someone has already set derby.infolog.append=true, and is
used to doing a lot of starting and shutting down, the derby.log could now grow
quite large quickly. So I worry about doing this by default...
Did you intend to backport such a change?
I was thinking perhaps sysinfo output could go to a separate log file, to show
up wherever derby.log lives...?
But likely I over-estimate the growth of derby.log; and I agree something more
than what we get currently will be useful.
> 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-1272-pre.diff, derby-1272-pre2.diff,
> derby-1272-pre3.diff, derby-1272-v4.diff, DERBY-1272v5.diff,
> DERBY-1272v6.diff, DERBY-1272v6.stat, DERBY-1272v8.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.
-
You can reply to this email to add a comment to the issue online.
