db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1272) Change sysinfo to print to error log (derby.log) on boot of derby if derby.stream.error.logSeverityLevel=0
Date Sat, 08 Jul 2006 01:18:30 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1272?page=all ]

Andrew McIntyre updated DERBY-1272:
-----------------------------------

    Attachment: derby-1272-v4.diff

Attaching updated patch which resolves the build failure noted in the previous comments and
adds setting logSeverityLevel=0 to the errorStream test as suggested by Kathey.

> 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
>         Type: Improvement

>   Components: Tools
>     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


Mime
View raw message