You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2013/04/23 21:45:15 UTC

[jira] [Created] (FELIX-4031) [DS] Respond better to InterruptedException

David Jencks created FELIX-4031:
-----------------------------------

             Summary: [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 ds annotations 1.2.2, scr-1.8.0
            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