[QPID-4021] Badly behaved clients can still clog up the broker

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.17
• Fix Version/s: 0.23
• Component/s: C++ Broker
• Assignee: Unassigned
• Reporter: Andrew Stitcher
• Created: 25/May/12 16:19
• Updated: 08/Sep/13 13:37
• Resolved: 04/Jun/13 14:40

Description

The recent code that timeouts out new connections that have not negotiated the protocol within (a default) 2 seconds still leaves a gap where badly behaved applications can tie up the broker.

The timeout should really be till either heartbeats are activated in which case they will take over the role of timing out idle connections. Or until the connection is authenticated in which case the policy on admitting users should take care of limiting the connections.

Issue Links

• relates to: QPID-2518 Qpid C++ broker can easily be blocked by client trying to connect over SSL port
• relates to: QPID-4925 [Java Broker] Timeout connections which do not complete connection handshake