[
https://issues.apache.org/jira/browse/DERBY-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223185#comment-13223185
]
Kristian Waagan commented on DERBY-5617:
----------------------------------------
The next step for this issue is backporting it (required by DERBY-5608). I'll
wait for a little while longer to allow people to analyze their test results
first, reducing the chance of backporting something that causes trouble.
> Improve process handling in SpawnedProcess
> ------------------------------------------
>
> Key: DERBY-5617
> URL: https://issues.apache.org/jira/browse/DERBY-5617
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.9.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.9.0.0
>
> Attachments: derby-5617-1a-spawnedprocess_improvements.diff,
> derby-5617-2a-join_destroy_ordering.diff,
> derby-5617-3a-timer_as_daemon_thread.diff
>
>
> SpawnedProcess wraps a java.lang.Process and performs various tasks related
> to process handling. Using external processes from Java is somewhat tricky,
> in part because of sub-optimal behavior in the methods provided by Process.
> I plan to implement the following improvements:
> a) Kill the process after a timeout (the clock starts ticking when you
> create the SpawnedProcess instance).
> b) Don't let interrupts stop SpawnedProcess from waiting for / terminating
> the process.
> c) Clean up the Process properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
