[
https://issues.apache.org/jira/browse/DERBY-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-6012:
-----------------------------------
Attachment: derby-6012-1a-error_reporting.diff
I've attached an incremental improvement for the error reporting as patch 1a,
and committed it to trunk with revision 1448941.
I don't know how hard it it to use the programmatic APIs, but I do know that
using the command line tools is non-trivial. There are also differences between
platforms. One issue is getting the id of the spawned process.
> 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: derby-6012-1a-error_reporting.diff,
> 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
