[
https://issues.apache.org/jira/browse/DERBY-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121109#comment-13121109
]
Dag H. Wanvik commented on DERBY-5444:
--------------------------------------
Changes look good, just wondering, what is the test use case for the way
interrupts are handled here? Is this code liable to be used in a context where
the current thread is being interrupted? (since you turn them back on
consistently - not that it should hurt)
> SpawnedProcess.complete may fail to destroy the process when a timeout is
> specified
> -----------------------------------------------------------------------------------
>
> Key: DERBY-5444
> URL: https://issues.apache.org/jira/browse/DERBY-5444
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.9.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Attachments: derby-5444-1a-destroy_on_timeout.diff
>
>
> The logic in SpawnedProcess has a weakness that may result in the wrapped
> process not being destroyed if the destroy variable is false and a timeout is
> specified.
> The problem is that the while condition will shortcut the if condition in the
> catch clause (where destroy is set to true if the timeout is exceeded).
--
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
