[
https://issues.apache.org/jira/browse/DERBY-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-6012:
-----------------------------------
Attachment: DERBY6012_patch2_diff.txt
Attaching a proof of concept patch where I am forcing the code to fail and
confirm that it is indeed doing java core dump and dumping the threads.(I had
to do teardown only for testing the force failure, it will not be part of the
actual commit). Actual code change will be something like following
//DERBY-6012 print thread dump and java core
StringBuffer sb = new StringBuffer(msg);
sb.append(ExceptionUtil.dumpThreads());
JVMInfo.javaDump();
fail(sb.toString());
If the idea of the actual code change looks good, I will go ahead and commit it
tomorrow.
> Print thread dump and dump javacore if NetworkServerTestSetup has to kill off
> the Network Server start up process due to timeout
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6012
> URL: https://issues.apache.org/jira/browse/DERBY-6012
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.8.3.0
> Environment:
> Reporter: Kathey Marsden
> Assignee: Mamta A. Satoor
> Fix For: 10.10.0.0
>
> Attachments: DERBY6012_patch1_diff.txt, DERBY6012_patch2_diff.txt
>
>
> If Network Server startup hangs or times out as in DERBY-5991, we should
> generate a javacore or a thread dump so the cause of the problem can be more
> easily diagnosed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
