[PROTON-372] driver does not handle POLLHUP

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.5
• Fix Version/s: proton-0.5
• Component/s: proton-c
• Environment: osx
• Assignee: Ted Ross
• Reporter: Božo Dragojevič
• Created: 30/Jul/13 07:04
• Updated: 02/Oct/19 19:17
• Resolved: 05/Aug/13 15:53

Description

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.