You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Bozo Dragojevic (JIRA)" <ji...@apache.org> on 2013/07/30 22:41:48 UTC
[jira] [Commented] (PROTON-372) driver does not handle POLLHUP
[ https://issues.apache.org/jira/browse/PROTON-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724377#comment-13724377 ]
Bozo Dragojevic commented on PROTON-372:
----------------------------------------
(gdb) p ssn
$1 = (pn_session_t *) 0x0
1679 // XXX: what if session is NULL?
> 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
> Attachments: 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