You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/02/01 14:55:39 UTC
[jira] [Updated] (QPID-7033) [Java Broker] Busy IO thread pools may
cause client connections to be unfairly closed
[ https://issues.apache.org/jira/browse/QPID-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-7033:
-----------------------------
Fix Version/s: qpid-java-6.1
> [Java Broker] Busy IO thread pools may cause client connections to be unfairly closed
> -------------------------------------------------------------------------------------
>
> Key: QPID-7033
> URL: https://issues.apache.org/jira/browse/QPID-7033
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0, qpid-java-6.0.1
> Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
>
> The Broker installs connection tickers to guard against a new connection that sends no bytes or sends bytes too slowly. If the ticker expires, the connection is closed with a {{CON-1003 : Closed due to inactivity}} message.
> However, currently a side effect of the Selector Thread's algorithm will mean that a connection that whilst ready for read but cannot be scheduled on an IO Pool sufficiently quickly enough will also be closed. This is unfair.
> This problem will mean that establishing connections to a busy broker may be unreliable. Also a retry effect on the client may exacerbate the situation.
--
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