You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2020/10/29 01:36:00 UTC
[jira] [Commented] (ARTEMIS-2966) Server.send does not support
ANYCAST with distinct queue names.
[ https://issues.apache.org/jira/browse/ARTEMIS-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222650#comment-17222650 ]
Clebert Suconic commented on ARTEMIS-2966:
------------------------------------------
this was broken back in 2017 after https://issues.apache.org/jira/browse/ARTEMIS-1416
which I think it was a mistake.
I added an extra check now to check if the bindings exists with a different name before auto-creating...
it's making an extra check for this.
> Server.send does not support ANYCAST with distinct queue names.
> ---------------------------------------------------------------
>
> Key: ARTEMIS-2966
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2966
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Clebert Suconic
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> if you send a message to an anycast address, and the queue name does not match, the operation is wrongly querying the queue instead of the address, what would cause either a new Queue auto created, or a misleading message with address does not exist.
> The fix here is as simple as using the address name to query the address.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)