[
https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922656#action_12922656
]
Kathey Marsden commented on DERBY-4856:
---------------------------------------
I recently had to do a programatic dump of information on a Sun JVM and found
this:
http://forums.oracle.com/forums/thread.jspa?threadID=1237584&tstart=15
The file did not have the system properties or shell environment. I printed
the system properties as below, but between the two seemed to still be missing
a of information, like the shell environment and the command line,
System.out.println("\n\n------ Java System Properties -----");
Properties sprops = System.getProperties();
Set listem;
String str;
listem = sprops.keySet();
Iterator itr = listem.iterator();
System.out.println("props test");
while (itr.hasNext())
{
str = (String) itr.next();
System.out.println("key: " + str +"\t;value: " +
sprops.getProperty(str));
}
System.out.println("---- end System Properties output ----\n\n");
> Add thread dump information when derby crash
> --------------------------------------------
>
> Key: DERBY-4856
> URL: https://issues.apache.org/jira/browse/DERBY-4856
> Project: Derby
> Issue Type: Bug
> Components: Services
> Reporter: Lily Wei
> Priority: Minor
>
> On system crash or session ending error, Derby should dump as much
> information as possible. Such as: forcing a javacore if possible or at least
> thread dump and system environment information. This should only occur if a
> running session crashes not on boot error due to fail recovery etc.
> The IBM jvm provides a way to programmatically dump a javacore. i.e.
> com.ibm.jvm.Dump.JavaDump() And, the SUN jvm will force a thread dump using
> the Unsafe class and there may be a better way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
