[
https://issues.apache.org/jira/browse/ARTEMIS-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy A. Bish resolved ARTEMIS-5444.
--------------------------------------
Fix Version/s: 2.42.0
Resolution: Fixed
> Refactor temp-queue-namespace
> -----------------------------
>
> Key: ARTEMIS-5444
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5444
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.42.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The {{temporary-queue-namespace}} attribute was added via ARTEMIS-2901 to
> deal with the fact that when JMS clients create temporary destinations (e.g.
> via {{Session.createTemporaryQueue()}} or {{Session.createTemporaryTopic()}})
> a UUID is used for the queue and/or address which means the name can't be
> matched via any address-setting other than {{#}}.
> The problem with the solution from ARTEMIS-2901 is that it was predicated on
> the fact that the resources were _temporary_. However, it turns out that this
> was a red herring. In the Core broker _any_ queue can be a temporary queue
> and applying the settings from the {{temporary-queue-namespace}} to temporary
> resources rather than the actual match (if it exists) produces confusing and
> undesired results.
> The real issue isn't that the resources are temporary, but rather that they
> are named with a UUID. Therefore, the broker should detect the UUID name and
> apply the namespace based on that. Also, {{temporary-queue-namespace}} should
> be renamed to be more clear.
> Technically speaking this change will result in a semantic change, but the
> change is from a buggy behavior to non-buggy behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
