[
https://issues.apache.org/jira/browse/AMQ-9685?focusedWorklogId=962284&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-962284
]
ASF GitHub Bot logged work on AMQ-9685:
---------------------------------------
Author: ASF GitHub Bot
Created on: 18/Mar/25 12:06
Start Date: 18/Mar/25 12:06
Worklog Time Spent: 10m
Work Description: cshannon commented on PR #1410:
URL: https://github.com/apache/activemq/pull/1410#issuecomment-2732980057
> Once a wrong named queue is created the broker is broken and not
restartable any more.
Ah ok, that was the part I was missing. So one thing to keep in mind when
creating a Jira or a PR is the more details for the motivation to help explain
why the change is necessary, the better. The jira only makes mention of the
exception when trying to make the consumer which makes a lot of sense.
I still do not see a reason to make any change here and things are working
as intended because:
1. The main point I was trying to make is creating a consumer or a producer
that matches the configured VT prefix and suffix, but is missing the actual
topic name, is a mistake and just continuing on without any error and allowing
the client to dynamically create that destination doesn't make any sense and
should be blocked. We shouldn't just hide the issue and allow things to carry
on.
2. The broker itself will also block you from creating a destination like
this if it is wrong. If the VirtualTopicInterceptor is created and the broker
config tries to create a destination like this it will break on start up and
should not create it. It would also break if trying to create it with JMX or
some other means so we prevent mistakes there which is good.
3. The only issue seems to be the edge case when the destination was created
by mistake somehow, probably before the interceptor was configured which would
mean the broker would no longer start up. While this is a problem obviously, in
that case it's a pretty easy fix and there is no risk of data loss. All you
need to do is disable the VirtualDestinationInterceptor configuration in the
broker config and then the broker would start up fine and you could delete the
bad destination before reconfiguring the interceptor.
Issue Time Tracking
-------------------
Worklog Id: (was: 962284)
Time Spent: 1h (was: 50m)
> Empty virtualName from broken queue name
> ----------------------------------------
>
> Key: AMQ-9685
> URL: https://issues.apache.org/jira/browse/AMQ-9685
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.19.0, 6.1.6
> Reporter: Benjamin Graf
> Priority: Major
> Labels: error, virtualtopic
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Accidentally "invalid" queue name can lead to broken broker after throwing
> "{{Invalid destination name: a non-empty name is required}}"
--
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
