[
https://issues.apache.org/jira/browse/QPID-8233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8233:
-----------------------------
Fix Version/s: qpid-java-broker-7.1.0
> [Broker-J][AMQP 1.0] Failure on connecting to a virtual host which is not yet
> active should use connection-forced error
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-8233
> URL: https://issues.apache.org/jira/browse/QPID-8233
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: 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
> Reporter: Rob Godfrey
> Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.7
>
> Attachments: QPID-8233.diff, apache-qpid-broker-j-7.0.3-bin.zip
>
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
