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 2009/11/12 23:44:39 UTC
[jira] Created: (DERBY-4441) Change sysinfo to print out more
specific JVM information
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
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.
Re: [jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by Myrna van Lunteren <m....@gmail.com>.
On Thu, Apr 1, 2010 at 7:08 PM, Myrna van Lunteren (JIRA)
<ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852665#action_12852665 ]
>
> Myrna van Lunteren commented on DERBY-4441:
> -------------------------------------------
>
> hm...I get the same without the patch.
> When I was using the patch, I tried classes and jars, insane and sane...
> I guess this is what Jayaram is seeing also...
>
Sorry for that comment - I failed to change my classpath after reverting.
Myrna
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851909#action_12851909 ]
Lily Wei commented on DERBY-4441:
---------------------------------
Thank you, Knut.
These are very good suggestion. I will fix the code and run tests after that. Does anyone run it against IBM jvm? I did not get any failure for SysInfoTest from sun jvm. However, I am not sure how they will behave with IBM jvm.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Updated: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-4441:
----------------------------------
Fix Version/s: 10.5.3.1
> 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.1.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Fix For: 10.5.3.1, 10.6.1.0
>
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441-7.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852627#action_12852627 ]
Myrna van Lunteren commented on DERBY-4441:
-------------------------------------------
after applying the patch, I ran with both ibm 1.6 and ibm 1.5 and jdk 1.6 with my machine.
The patched test passes with jdk 1.6, but fails with ibm 1.6 and ibm 1.5.
I cannot look into why right now.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777262#action_12777262 ]
Knut Anders Hatlen commented on DERBY-4441:
-------------------------------------------
Sun's JVM also has the java.runtime.version property, but not java.fullversion. Dumping the value of these properties if they are present, and ignoring them if they're not, sounds like a good idea.
> 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
>
> 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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859882#action_12859882 ]
Kim Haase commented on DERBY-4441:
----------------------------------
It looks as if the result of this fix is to add one line (java.runtime.version) to the sysinfo output. Is this correct?
We need to change the sysinfo example in the Tools manual slightly to reflect this change. I'll file a doc issue.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441-7.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Closed: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden closed DERBY-4441.
---------------------------------
Assignee: Lily Wei (was: Kathey Marsden)
Resolution: Fixed
closing back up after port.
> 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.1.0
> Reporter: Kathey Marsden
> Assignee: Lily Wei
> Priority: Minor
> Fix For: 10.5.3.1, 10.6.1.0
>
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441-7.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Updated: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lily Wei updated DERBY-4441:
----------------------------
Comment: was deleted
(was: Thank you for reviewing the patch, Kristian. I will prefer using spaces for indentation as well.
However, for file BaseDataFileFactory.java, there are way too many lines changes if I save spaces as tab for indentation using editor/IDE to insert spaces when I press the TAB key. That is why both spaces and tab were using for the patch. I think it is also important to keep history as we introduce insert spaces as tab for indentation going forward. We could have a project that only changes tab to spaces.
)
> 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.1.0
> Reporter: Kathey Marsden
> Assignee: Lily Wei
> Priority: Minor
> Fix For: 10.5.3.1, 10.6.1.0
>
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441-7.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859898#action_12859898 ]
Lily Wei commented on DERBY-4441:
---------------------------------
Thanks, Kim. The result of this fix is to add one line (java.runtime.version) to the sysinfo output for sun jvm. For ibm jvm, it will add two line (java.runtime.version and java.fullversion)
This is the example from sun jvm output for sysinfo:
Java user dir: c:\derby\trunk\testtmp
java.specification.name: Java Platform API Specification
java.specification.version: 1.6
java.runtime.version: 1.6.0_17-b04 <<<====NEW======>>>
This is the example for ibm jvm output for sysinfo:
Java user dir: c:\derby\trunk
java.specification.name: Java Platform API Specification
java.specification.version: 1.6
java.runtime.version: jvmwi3260sr7-20091214_49398 <<<====NEW======>>>
java.fullversion: JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr7-20091214_49 <<<====NEW======>>>
398 (JIT enabled, AOT enabled) <<<====NEW======>>>
J9VM - 20091214_049398 <<<====NEW======>>>
JIT - r9_20091123_13891 <<<====NEW======>>>
GC - 20091111_AA <<<====NEW======>>>
Kathey also suggests to add more info to the change of policy file. Will you mind include that in the doc as well.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441-7.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846478#action_12846478 ]
Kathey Marsden commented on DERBY-4441:
---------------------------------------
My suites.All run was less than successful. This morning my screen was black and I had to reboot. The last output of my run was:
testPositionString used 656 ms .
testPositionStringWithUnicode used 2032 ms .
testPositionClob
I am not sure how long it took for things to go south. Before that, there were failures in
DerbyNetClient/SysinfoTest
testSysinfo used 1984 ms F.
testSysinfoMethod used 47 ms F.
testSysinfoLocale used 2109 ms F.
testSysinfo used 1969 ms F.
testSysinfoMethod used 47 ms F.
but that did not seem to be what held up the run as it continued for some time after that.
I will try the one test with testPositionClob and see if it runs ok and then do a full rerun. I can't imagine how a sysinfo change could cause such problems.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441_diff.txt, 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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858050#action_12858050 ]
Kathey Marsden commented on DERBY-4441:
---------------------------------------
Ok. Thanks Lily, I will pick up the 6 patch and commit it Monday, so this useful enhancement will make 10.6. Have a great weekend.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ 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-3_diff.txt
Add permission for java.io.FilePermission "${derby.system.home}${/}derby.log", "read, write, delete" with the new patch.
I run suites all and derbyall test suites. Both passed with Windows 7 on sun jvm.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Updated: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ 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-4.diff.txt
Thanks, Knut.
I include the new patch for this bug.
The changes include:
1. Move places further left for printPropertyIfNotNull()
2. add @param tags or two getJavProperty methods. Don't want to have java warning.
3.Add the comment to explain nullUnavailable parameter for the two-argument getJavaProperty() method.
I run tests for Suits.all and derbyall. They passed with sun jvm on Windows 7 env.
I did not run test against ibm jvm. The patch is ready if we don't have any diff against ibm jvm.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852665#action_12852665 ]
Myrna van Lunteren commented on DERBY-4441:
-------------------------------------------
hm...I get the same without the patch.
When I was using the patch, I tried classes and jars, insane and sane...
I guess this is what Jayaram is seeing also...
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851769#action_12851769 ]
Knut Anders Hatlen commented on DERBY-4441:
-------------------------------------------
Hi Lily,
The #3 patch looks safe to me. My only comments are
- the new method printPropertyIfNotNull() is placed further to the left than the surrounding methods
- the @param tags in the two getJavaProperty() methods are empty. I think this will cause javadoc warnings
- it would be good if the javadoc comment for the two-argument getJavaProperty() method explained the purpose of the nullUnavailable parameter
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851657#action_12851657 ]
Lily Wei commented on DERBY-4441:
---------------------------------
Would someone help me look at this patch? I will really appricated help at this point. Thank you so much!
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842757#action_12842757 ]
Lily Wei commented on DERBY-4441:
---------------------------------
Good point. I can change the behavior to reflect that. Any other info we should print out with JAVA information?
> 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
> Assignee: Lily Wei
> 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.
[jira] Updated: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ 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
Add method to handle property that is not available from the jvm. In this version, it is handling java.runtime.version and 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441_diff.txt, 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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden closed DERBY-4441.
---------------------------------
Thanks Lily for the fix
> 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.1.0
> Reporter: Kathey Marsden
> Assignee: Lily Wei
> Priority: Minor
> Fix For: 10.6.1.0
>
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441-7.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847400#action_12847400 ]
Kathey Marsden commented on DERBY-4441:
---------------------------------------
I wanted to mention that the black screen and necessary reboot happened to me running tests with a completely different patch, so I think it is unrelated to Lily's patch, but rather some hardware problem with the machine.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Updated: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ 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-6.diff.txt
With this patch, it passed all the tests for derbyall and suites.all. However, with ibm 1.6 jvm, SysinfoTest.testSysinfoLocale failed with expect <15> was <1>. I think this failure happends against german locale when connect to network server with ibm 1.6 jvm with windows 7 64 bits platform. However, just want to provide the current patch so it is available.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lily Wei reassigned DERBY-4441:
-------------------------------
Assignee: Lily Wei
> 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
> Assignee: Lily Wei
> 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.
[jira] Updated: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-4441:
--------------------------------------
Comment: was deleted
(was: hm...I get the same without the patch.
When I was using the patch, I tried classes and jars, insane and sane...
I guess this is what Jayaram is seeing also...)
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Reopened: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden reopened DERBY-4441:
-----------------------------------
Assignee: Kathey Marsden (was: Lily Wei)
reopen for 10.5 backport
> 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.1.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Fix For: 10.6.1.0
>
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441-7.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858012#action_12858012 ]
Kathey Marsden commented on DERBY-4441:
---------------------------------------
Hi Lily I applied patch 5 and tested SysinfoTest with IBM 1.6 on XP
java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr7-20091217_01(SR7))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr7-200912
14_49398 (JIT enabled, AOT enabled)
J9VM - 20091214_049398
JIT - r9_20091123_13891
GC - 20091111_AA)
JCL - 20091202_01
It passed fine and I agree your failure is probably an IB47 M 1.6 on Windows 7 64bit issue, because a similar problem was reported from someone else running tests on Windows 7 64 bit. I think you should file a separate issue for that, but it should not hold your patch up because people are seeing it without your patch.
I was getting ready to commit your 5 patch, but see now there is a 6 patch. What is the difference between 5 and 6?
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892962#action_12892962 ]
Lily Wei commented on DERBY-4441:
---------------------------------
Thank you for reviewing the patch, Kristian. I will prefer using spaces for indentation as well.
However, for file BaseDataFileFactory.java, there are way too many lines changes if I save spaces as tab for indentation using editor/IDE to insert spaces when I press the TAB key. That is why both spaces and tab were using for the patch. I think it is also important to keep history as we introduce insert spaces as tab for indentation going forward. We could have a project that only changes tab to spaces.
> 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.1.0
> Reporter: Kathey Marsden
> Assignee: Lily Wei
> Priority: Minor
> Fix For: 10.5.3.1, 10.6.1.0
>
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441-7.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Updated: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ 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-5.diff.txt
Thanks to Kathey. I have ibm 1.6 jvm. Make changes on policy and make SysinfoTest.sysinfotest passed. However, there is still one failure on SysinfoTest with ibm 1.6 jvm
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ 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-7.diff.txt
When looking at the regression run. Revision 935871 passed on jvm 1.4, 1.6, javame. It failed on jvm 1.5 with 49 failure and 6 errors. i.e. changeEncryptionFromNone.
For ibm jvm, revision 935786 seems to be ok on Linux. It did not have windows result yet.
I am attaching the 10.5 port in case it is safe to use it.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441-7.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846297#action_12846297 ]
Lily Wei commented on DERBY-4441:
---------------------------------
Thank you so much, Kathey. It is so great to know this. I am still in the middle of finding out the problem with my Vista. Vista is a challenging operating system.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441_diff.txt, 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.
[jira] Updated: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-4441:
----------------------------------
Attachment: suites.All.withdiff2.txt
Lily, I did another run and this time had none of the strange behavior, but just the six sysinfo failures reported in the attached suites.Allwithdiff2.txt. Maybe I too am having trouble with my machine and actually have a new one in a box here on my desk. After you fix the sysinfo failures, I'll give it another run on the new machine to make sure.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Updated: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ 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-2_diff.txt
Along with Main.java change, all the policy files should include java.runtime.version and java.fullversion. This patch include that.
The derbyall test passed with this patch. I am running Suites.All test suit.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441_diff.txt, 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.
[jira] Resolved: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lily Wei resolved DERBY-4441.
-----------------------------
Fix Version/s: 10.6.0.0
Resolution: Fixed
It looks like regression is ok and 10.5 patch is attached. I am closing this issue for now.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Fix For: 10.6.0.0
>
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441-7.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858023#action_12858023 ]
Lily Wei commented on DERBY-4441:
---------------------------------
Thank you so much, Kathey. The difference between 5 and 6 is taking out of write permission for java.runtime.version and java.fullversion. I think version 6 is cleaner than 5. It is so good to learn that it is ready to commit.
I will create another issue for SysinfoTest.testsysinfoLocale failed with IB47M 1.6 on Windows 7 64 bit.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441-3_diff.txt, DERBY-4441-4.diff.txt, DERBY-4441-5.diff.txt, DERBY-4441-6.diff.txt, DERBY-4441_diff.txt, DERBY-4441_diff.txt, suites.All.withdiff2.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843311#action_12843311 ]
Lily Wei commented on DERBY-4441:
---------------------------------
Will someone please try ibm jvm, mac and any other jvm to see. Also, please let me know if there is any useful property to use. I did not run any test yet.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441_diff.txt, 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.
[jira] Updated: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lily Wei updated DERBY-4441:
----------------------------
Issue & fix info: [High Value Fix, Newcomer, Patch Available] (was: [High Value Fix, Newcomer])
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441_diff.txt, 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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846488#action_12846488 ]
Lily Wei commented on DERBY-4441:
---------------------------------
Oh, no. It is a great things we have regression tests to catch for things like this.
I will run only DerbyNetClient/Sysinfo to see which policy file change causes such severe behavior. From there, I will also check where it hangs on my machine to see the impact of policy file changes.
Thank you so much Kathey for looking into this.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441_diff.txt, 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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846207#action_12846207 ]
Kathey Marsden commented on DERBY-4441:
---------------------------------------
Lily told me this morning that with this patch she was seeing a hang in memory.TriggerTests. I applied the 2_diff patch and ran the test with no problems. I will run the full suites.All now.
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441-2_diff.txt, DERBY-4441_diff.txt, 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.
[jira] Commented: (DERBY-4441) Change sysinfo to print out more
specific JVM information
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843330#action_12843330 ]
Kathey Marsden commented on DERBY-4441:
---------------------------------------
Hi Lily,
It looks great with the IBM 1.6, 1.5 and 1.42 jvms. Here is the 1.6 output.
[C:/svn4/trunk] java org.apache.derby.tools.sysinfo
------------------ Java Information ------------------
Java Version: 1.6.0
Java Vendor: IBM Corporation
Java home: C:\p4\marsden_trunk\ibm16\jre
Java classpath: .;C:/svn4/trunk/jars/sane/derbytools.jar;C:/svn4/trunk/jars/sane/derbyrun.jar;C:/svn4/trunk/jars/sane/d
erbyclient.jar;C:/svn4/trunk/jars/sane/derbynet.jar;C:/svn4/trunk/jars/sane/derbyTesting.jar;C:/svn4/trunk/tools/java/ju
nit.jar;c:/svn/tools/jakarta-oro-2.0.8.jar
OS name: Windows XP
OS architecture: x86
OS version: 5.1 build 2600 Service Pack 3
Java user name: kmarsden
Java user home: C:\Documents and Settings\kmarsden
Java user dir: C:\svn4\trunk
java.specification.name: Java Platform API Specification
java.specification.version: 1.6
java.runtime.version: jvmwi3260sr5-20090519_35743
java.fullversion: J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr5-20090519_35743 (JIT enabled, AOT enabled)
J9VM - 20090519_035743_lHdSMr
JIT - r9_20090518_2017
GC - 20090417_AA
--------- Derby Information --------
JRE - JDBC: Java SE 6 - JDBC 4.0
[C:\svn4\trunk\jars\sane\derby.jar] 10.6.0.0 alpha - (921154M)
...
> 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
> Assignee: Lily Wei
> Priority: Minor
> Attachments: DERBY-4441_diff.txt, 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.