[
https://issues.apache.org/jira/browse/QPID-8233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590049#comment-16590049
]
Rob Godfrey commented on QPID-8233:
-----------------------------------
Attached are a patch and a full build of Broker-J 7.0.3 with this patch applied
to see if this approach solves the problem detailed in PROTON-1917
> [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
> Reporter: Rob Godfrey
> Priority: Major
> 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: [email protected]
For additional commands, e-mail: [email protected]
