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 Wed, 18 May 2011 16:50:47 GMT

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

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

I think now  what is needed from  sysinfo is now logged to derby.log by default with the diagnostics
added in various other issues. We have 
  - The full derby version for derby.jar
  - The class loader that loads derby. 
  - The location from which derby.jar was loaded.
  - The full java version
  - The user.dir and derby.system.home  locations.
  - The log location if it has been redirected.

The only things that are missing from sysinfo are the full classpath, the exact version of
other derby jar files  and the OS information . 

 I don't think that the non-derby classpath entries are usually  relevant for embedded derby
support  when looking at the derby.log and actually having the full classpath might be information
users don't wish to share with the list.  Regarding the versions of the other derby.jar files,
I could see that in rare cases it might be relevant if versions are mixed but in those  cases,
the client or tools or whatever would typically have a separate running environment where
sysinfo output would be more relevant.  Also adding these things would add bulk to the boot
message.

I do think the OS information would be useful to have, e.g,
OS name:         Windows XP
OS architecture: x86
OS version:      5.1 build 2600 Service Pack 3

So if nobody objects. I would like to open an issue to add the OS  info to the boot message
and close this issue.










> 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-1272v5.diff, DERBY-1272v6.diff, DERBY-1272v6.stat, DERBY-1272v8.diff,
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message