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 2017/06/26 09:13:00 UTC
[jira] [Resolved] (QPID-7806) [Java Broker] [AMQP 1.0] Slow
connection ticker should be running until OPEN performative is received or
timeout expires
[ https://issues.apache.org/jira/browse/QPID-7806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall resolved QPID-7806.
------------------------------
Resolution: Fixed
Change looks reasonable to me.
> [Java Broker] [AMQP 1.0] Slow connection ticker should be running until OPEN performative is received or timeout expires
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7806
> URL: https://issues.apache.org/jira/browse/QPID-7806
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: qpid-java-broker-7.0.0
> Reporter: Alex Rudyy
> Fix For: qpid-java-broker-7.0.0
>
>
> Slow connection ticker is running until one of the following condition is true:
> * authenticated subject is set on a connection
> * timeout expires
> In AMQP 1.0 connection the subject is set on finishing SASL negotiation before receiving AMQP header and OPEN performative. If authenticated client will not send AMQP header or/and OPEN performative (or sending of them will take unreasonably long of time) due to bug or malicious intention, the Broker might end up with not fully established connections consuming system resources. We need to protect Broker and run Slow connection ticker on AMQP 1.0 until OPEN is received and idle timeout is negotiated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org