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] Commented: (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 00:10:30 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1272?page=comments#action_12419799 ] 

Andrew McIntyre commented on DERBY-1272:
----------------------------------------

1) Are you sure you grabbed the right patch? The build.xml change in the -pre3 patch (which
was absent from the -pre1 patch) should have taken care of the problem in #1. Check that your
java/engine/org/apache/derby/impl/services/build.xml has been modified to include ${derby.tools.src.dir}
in the srcdir for the compile. If you do have this change in the build.xml, and are still
getting this problem, I'll take another look.

2) a good idea. But then see also #3. I'm not sure how often tests are being run with sane
builds, if at all, though.

3) as it is, sysinfo will always be printed in sane builds, so maybe you were running with
a sane build? you liked this aspect of the patch last time you looked at it. :-)

4) While that would be nice, the reason that I put it where it is in the code is that sysinfo
will still be dumped to derby.log even if the engine fails to boot due to some catastrophic
error. I'm not sure if it is worth the effort to delay printing sysinfo until after the boot
message has printed in order to get pretty formatting for something that is meant to be a
diagnostic for serious failures.

> 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
>
> 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