You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (Resolved) (JIRA)" <ji...@apache.org> on 2012/04/17 16:04:18 UTC
[jira] [Resolved] (DERBY-5617) Improve process handling in
SpawnedProcess
[ https://issues.apache.org/jira/browse/DERBY-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan resolved DERBY-5617.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.8.2.3
Backported to 10.8, together with DERBY-5608, with revision 1327102.
Resolving issue.
> 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.8.2.3, 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