[
https://issues.apache.org/jira/browse/AMQ-9685?focusedWorklogId=962384&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-962384
]
ASF GitHub Bot logged work on AMQ-9685:
---------------------------------------
Author: ASF GitHub Bot
Created on: 18/Mar/25 17:30
Start Date: 18/Mar/25 17:30
Worklog Time Spent: 10m
Work Description: graben commented on PR #1410:
URL: https://github.com/apache/activemq/pull/1410#issuecomment-2734138093
That's not completely correct. The broker allows creating the broken
destination at runtime. It's even persistently registered but a loop of
exception occurs in the log until shutdown and reparation. Not a really good
option for large scale productive systems! With this patch you would be able to
correct at runtime without any broker change or downtime periods.
Issue Time Tracking
-------------------
Worklog Id: (was: 962384)
Time Spent: 1h 10m (was: 1h)
> 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 10m
> 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
