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

Posted to proton@qpid.apache.org by "Ted Ross (JIRA)" <ji...@apache.org> on 2013/08/05 17:54:48 UTC

[jira] [Resolved] (PROTON-372) driver does not handle POLLHUP

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

Ted Ross resolved PROTON-372.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 0.5
    
> driver does not handle POLLHUP
> ------------------------------
>
>                 Key: PROTON-372
>                 URL: https://issues.apache.org/jira/browse/PROTON-372
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.5
>         Environment: osx
>            Reporter: Bozo Dragojevic
>            Assignee: Ted Ross
>             Fix For: 0.5
>
>         Attachments: 0001-Handle-POLLHUP-as-pending-io.patch, 0001-Handle-POLLHUP-as-POLLERR.patch, confuse-driver.py
>
>
> If a peer closes the socket at an inopportune time poll() will start returning POLLHUP but not POLLERR. this drives messenger into a busyloop as the driver does not check this flag.
> The messenger instance is still able to service other connections but it's doing so at 100% cpu load as every poll() call returns immediately.

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