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

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

Commit e7df0285db50cb0b62cd5b35d2c60e22477f64bc in artemis's branch 
refs/heads/main from Timothy Bish
[ https://gitbox.apache.org/repos/asf?p=artemis.git;h=e7df0285db ]

ARTEMIS-5914 Bypass link creation in remote federation when possible

Bypass link creation from the target broker back to the source when remote
federation is configured if the outcome is known to be a failure due to the
federation user not having access to send into the queue on the remote.


> AMQP Remote federation receiver links optimization
> --------------------------------------------------
>
>                 Key: ARTEMIS-5914
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5914
>             Project: Artemis
>          Issue Type: Improvement
>          Components: AMQP, Federation
>    Affects Versions: 2.51.0
>            Reporter: Timothy A. Bish
>            Assignee: Timothy A. Bish
>            Priority: Minor
>             Fix For: 2.52.0
>
>
> When remote federation is configured and a policy sent to the remote target 
> to instruct it to federate message to itself from the source broker the 
> federation acts under the permissions of the logged in user. If user 
> permissions are such that the user cannot write into an address or queue that 
> it has been configured to bring the federated messages to it does not need to 
> bother creating the federation receiver link that will eventually fail to 
> route messages which reduces resource utilization by the target.  It should 
> log information indicating that is has bypassed federation due to access 
> issues to make it visible what has happened though.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to