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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2010/03/08 18:51:27 UTC
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842752#action_12842752 ]
Kathey Marsden commented on DERBY-4441:
---------------------------------------
I think if property info is not set it should be skipped instead of printing <info unavailable>. Otherwise it looks like the right general idea. With the IBM jvm you should see lots of detail in java.fullversion
> Change sysinfo to print out more specific JVM information
> ---------------------------------------------------------
>
> Key: DERBY-4441
> URL: https://issues.apache.org/jira/browse/DERBY-4441
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 10.3.3.1, 10.4.2.1, 10.5.3.1, 10.6.0.0
> Reporter: Kathey Marsden
> Priority: Minor
> Attachments: DERBY-4441_diff.txt
>
>
> It would be nice if sysinfo printed out more specific jvm information that is provided with java -version. At least with the IBM jvm the system properties java.runtime.version and java.fullversion give some more (but not all) information. More research is needed across multiple jvms to tie it down. Alternatively sysinfo could dump *all* the system property information, but that could make the output pretty big and show irrelavant information in some contexts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.