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