Return-Path: 
 <derby-dev-return-76393-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 7724 invoked from network); 8 Mar 2010 17:30:14 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 8 Mar 2010 17:30:14 -0000
Received: (qmail 98840 invoked by uid 500); 8 Mar 2010 17:29:50 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 98810 invoked by uid 500); 8 Mar 2010 17:29:50 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 98802 invoked by uid 99); 8 Mar 2010 17:29:50 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Mar 2010 17:29:50 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Mar 2010 17:29:49 +0000
Received: from brutus.apache.org (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 3520E234C052
	for <derby-dev@db.apache.org>; Mon,  8 Mar 2010 17:29:27 +0000 (UTC)
Message-ID: <1373880632.138901268069367216.JavaMail.jira@brutus.apache.org>
Date: Mon, 8 Mar 2010 17:29:27 +0000 (UTC)
From: "Lily Wei (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4441) Change sysinfo to print out more
 specific JVM information
In-Reply-To: <1648474455.1258065879824.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lily Wei updated DERBY-4441:
----------------------------

    Attachment: DERBY-4441_diff.txt

I did not do a lot of research. I am trying to get the feeling of whether this is the way we are thinking of solving this problem. 

>From this patch: This is what I see from sysinfo:
------------------ Java Information ------------------
Java Version:    1.6.0_13
Java Vendor:     Sun Microsystems Inc.
Java home:       C:\Program Files (x86)\Java\jre6
Java classpath:  .;c:/derby/trunk/tools/java/junit.jar;c:/derby/trunk/jars/sane/
derbyrun.jar;c:/derby/trunk/jars/sane/derbyTesting.jar;c:/derby/trunk/tools/java
/jakarta-oro-2.0.8.jar
OS name:         Windows Vista
OS architecture: x86
OS version:      6.0
Java user name:  lily
Java user home:  C:\Users\lily
Java user dir:   c:\derby\trunk
java.specification.name: Java Platform API Specification
java.specification.version: 1.6
java.runtime.version: 1.6.0_13-b03
java.fullversion: <info unavailable>
...

Any comment is welcome.

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