db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@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 Thu, 20 Sep 2007 21:18:51 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529264
] 

Kathey Marsden commented on DERBY-1272:
---------------------------------------

I think just changing the build.xml as follows will restrict the access to sysinfo
     srcdir="${derby.engine.src.dir};${derby.tools.src.dir}/org/apache/derby/impl/tools/sysinfo"

I think we should go ahead and check in this change even though the sysinfo output for the
security exceptions is not ideal.  That can  be handled separately as DERBY-1273

Any objections to checking in this change?

Kathey


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


Mime
View raw message