[QPID-8233] [Broker-J][AMQP 1.0] Failure on connecting to a virtual host which is not yet active should use connection-forced error

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, qpid-java-broker-7.0.0, qpid-java-broker-7.0.1, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, qpid-java-broker-7.0.6
• Fix Version/s: qpid-java-broker-7.1.0, qpid-java-broker-7.0.7
• Component/s: Broker-J
• Assignee: Alex Rudyy
• Reporter: Robert Godfrey
• Created: 23/Aug/18 10:29
• Updated: 05/Jan/19 20:01
• Resolved: 10/Sep/18 21:24

Description

Currently if a connection is made to a broker where a virtual host is in the process of activating, the client received a "not-found" error with a description "virtual host is not active". A client receiving this would not expect that simply retrying is likely to lead to success.

Instead of sending "not-found" the broker should send "connection-forced" which, while still inaccurate, at least indicates that the client should retry

Issue Links

• Blocked: QPID-8234 [Broker-J] Return amqp error "amqp:connection:forced" on opening connections to non-existing or not-active virtual hosts