You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Ramin Moazeni (JIRA)" <ji...@apache.org> on 2007/11/06 17:04:51 UTC
[jira] Updated: (DERBY-1272) Change sysinfo to print to error log
(derby.log) on boot of derby if derby.stream.error.logSeverityLevel=0
[ https://issues.apache.org/jira/browse/DERBY-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramin Moazeni updated DERBY-1272:
---------------------------------
Attachment: DERBY-1272v6.stat
DERBY-1272v6.diff
Hello,
I am attaching the v6 patch with this issue.
I appreciate your review/comments.
For testing this issue, I added a test for this issue to tools/DerbyLogTest.java.
Please note that by using
srcdir="${derby.engine.src.dir};${derby.tools.src.dir}/org/apache/derby/impl/tools/sysinfo"
I still got errors during build.
I got errors during suites.All while running this test which was resolved by
changing the order of the junit tests. I will file a separate jira issue for
that.
Thanks
Ramin Moazeni
> 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
> Assignee: Ramin Moazeni
> 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
>
>
> 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.