[
https://issues.apache.org/jira/browse/DERBY-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536582#comment-13536582
]
Mamta A. Satoor commented on DERBY-6012:
----------------------------------------
I should have tried to hand force the failure and see what happens. I just ran
the suite with the changes and since there was no failure, I didn't notice
fail(msg) preventing the new code from executing.
I probably should first call JVMInfo.javaDump(); and then use a StringBuffer to
collect the existing error info and add to it the thread dump info and call
fail on that string as shown below.
JVMInfo.javaDump();
StringBuffer sb = new StringBuffer(msg);
sb.append(ExceptionUtil.dumpThreads());
fail(sb.toString());
The code above will replace the existing fail(msg) call;
Let me if that sounds correct.
> 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
>
>
> 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
