[
https://issues.apache.org/jira/browse/AMQ-9685?focusedWorklogId=962233&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-962233
]
ASF GitHub Bot logged work on AMQ-9685:
---------------------------------------
Author: ASF GitHub Bot
Created on: 18/Mar/25 08:19
Start Date: 18/Mar/25 08:19
Worklog Time Spent: 10m
Work Description: graben commented on PR #1410:
URL: https://github.com/apache/activemq/pull/1410#issuecomment-2732069550
Well, like most issues it is Murphy's law who is causing misconfigurations.
Once a wrong named queue is created the broker is broken and not restartable
any more. This might cause full data loss if you aren't able to manipulate your
persistent backend! IMHO it doesn't make sense to allow an empty pattern by
wildcard that is causing an exception because it is empty. Misconfigurations
happen and shouldn't have that bad impact!
Issue Time Tracking
-------------------
Worklog Id: (was: 962233)
Time Spent: 50m (was: 40m)
> 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: 50m
> 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
