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

Posted to issues@trafficserver.apache.org by "Brian Geffon (JIRA)" <ji...@apache.org> on 2013/01/12 01:16:13 UTC

[jira] [Updated] (TS-1650) Inactivity cop should use TRY_LOCK instead of LOCK to avoid deadlock.

     [ https://issues.apache.org/jira/browse/TS-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Geffon updated TS-1650:
-----------------------------

    Description: In situations where a connection may have died while holding on to a mutex this can result in deadlock. Inactivity cop's only job is to cleanup and since it's trying to LOCK it will block. Instead we should just use a TRY_LOCK and continue cleaning up the remaining connections.  (was: In situations where a connection may have died while holding on to a mutex this can result in deadlock. Inactivity cops only job is to cleanup, and since it's trying to LOCK it will block. Instead we should just use a TRY_LOCK and continue cleaning up the remaining connections.)
    
> Inactivity cop should use TRY_LOCK instead of LOCK to avoid deadlock.
> ---------------------------------------------------------------------
>
>                 Key: TS-1650
>                 URL: https://issues.apache.org/jira/browse/TS-1650
>             Project: Traffic Server
>          Issue Type: Bug
>    Affects Versions: 3.3.0
>            Reporter: Brian Geffon
>            Assignee: Brian Geffon
>             Fix For: 3.3.1
>
>
> In situations where a connection may have died while holding on to a mutex this can result in deadlock. Inactivity cop's only job is to cleanup and since it's trying to LOCK it will block. Instead we should just use a TRY_LOCK and continue cleaning up the remaining connections.

--
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