You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2016/08/10 15:33:20 UTC
[jira] [Updated] (QPID-2968) Blocking on dead sockets
[ https://issues.apache.org/jira/browse/QPID-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Ross updated QPID-2968:
------------------------------
Fix Version/s: (was: Future)
> Blocking on dead sockets
> ------------------------
>
> Key: QPID-2968
> URL: https://issues.apache.org/jira/browse/QPID-2968
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
> Affects Versions: 0.7, 0.8, 0.9, Future
> Environment: Does not matter
> Reporter: Dmitry Konishchev
> Assignee: Rafael H. Schloming
> Labels: patch
> Attachments: patch
>
>
> * If you open a few connections, and one of them breaks (for example,
> due to a network error), another connections can be locked for time, which is
> equal to network timeout of the broken connection. This happens due to
> working with sockets in blocking mode and due to using one Selector for all
> connections.
> * All connections could become locked forever due to races between
> Driver and Selector objects. Driver object removes itself from the Selector
> non-atomically and a situation when Driver is alredy closed, but the Selector
> refers to it could happen. In this case select() call in the Selector raise
> an exeption due to self._transport.fileno() call on Driver where
> self._transport is None. The selector doesn't handle errors on select(), so
> the selector's thread will be stopped due to unhandled Exception.
> * There is no checks on EINTR error on os.* calls.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org