[
https://issues.apache.org/jira/browse/FELIX-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks resolved FELIX-4031.
---------------------------------
Resolution: Fixed
Fixed in rev 1471172
> [DS] Respond better to InterruptedException
> -------------------------------------------
>
> Key: FELIX-4031
> URL: https://issues.apache.org/jira/browse/FELIX-4031
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.8.0, scr ds annotations 1.2.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: scr-1.8.0
>
>
> Most of the locks in ds have a timeout. After reading about interruption and
> thinking I think that the proper response to an InterruptedException is to
> keep waiting for the timeout to expire, but give up if interrupted a second
> time. The interruption is supposed to be a hint to not continue forever, but
> the timeout is already doing that for us.
> We could track the time when we start the lock and only wait until the
> original timeout would have expired, but I think this would slow down normal
> operations too much for very minimal gain.
> In any case we should reset the interrupted flag. (already done in rev
> 1470394)
--
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
