[ https://issues.apache.org/jira/browse/QPID-8288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-8288: --------------------------------- Affects Version/s: (was: qpid-cpp-1.38.0) qpid-cpp-1.39.0 Fix Version/s: (was: qpid-cpp-1.39.0) qpid-cpp-1.40.0 > timeout on connection that is not writable does not cleanup on primary > ---------------------------------------------------------------------- > > Key: QPID-8288 > URL: https://issues.apache.org/jira/browse/QPID-8288 > Project: Qpid > Issue Type: Bug > Components: C++ Broker > Affects Versions: qpid-cpp-1.39.0 > Reporter: Gordon Sim > Assignee: Gordon Sim > Priority: Major > Fix For: qpid-cpp-1.40.0 > > > If an incoming socket from a backup is not writable at the point it times > out, then the sessions get cleaned up but the connection observers are not > notified of the closed connection (as the code used by the io layer is not > yet deleted; it is only deleted when the socket is writable). > For the primary in an ha cluster this means it does not fully handle the lost > connection. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org