You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/10/07 09:56:00 UTC

[jira] [Commented] (ARTEMIS-3520) include failure hint in Open frame sent when broker-balancer rejects or redirects AMQP connection

    [ https://issues.apache.org/jira/browse/ARTEMIS-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425450#comment-17425450 ] 

ASF subversion and git services commented on ARTEMIS-3520:
----------------------------------------------------------

Commit d7f37ae313bd3f26ed58ee08d2ca562c604b04b1 in activemq-artemis's branch refs/heads/main from Robbie Gemmell
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=d7f37ae ]

ARTEMIS-3520: set the Open failure hint when balancer redirects or refuses AMQP connection, add lower level test for balancer related redirect/refusal protocol behaviour


> include failure hint in Open frame sent when broker-balancer rejects or redirects AMQP connection
> -------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-3520
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3520
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 2.18.0
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Minor
>             Fix For: 2.19.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When the broker-balancer feature (ARTEMIS-3365) is refusing or redirecting AMQP connections, it doesnt include a failure hint property in the Open frame the same way it does for cases such as e.g ClientID enforcement. Some clients/applications can use this hint to know a Close frame is going to follow with e.g redirect details or a forced closure and avoid starting further work that is then going to fail.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)