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.