[
https://issues.apache.org/jira/browse/ARTEMIS-4924?focusedWorklogId=926322&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-926322
]
ASF GitHub Bot logged work on ARTEMIS-4924:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 17/Jul/24 08:36
Start Date: 17/Jul/24 08:36
Worklog Time Spent: 10m
Work Description: gtully commented on PR #5091:
URL:
https://github.com/apache/activemq-artemis/pull/5091#issuecomment-2232750976
I think we already have a way to prevent sending with rbac if that is the
problem.
But we may just need to make use of a dlq for invalid messages in this case.
This cause seems like a good match for a dlq as it blocks the head.
Issue Time Tracking
-------------------
Worklog Id: (was: 926322)
Time Spent: 20m (was: 10m)
> Do not allow sending messages directly to store-and-forward queues
> ------------------------------------------------------------------
>
> Key: ARTEMIS-4924
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4924
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 2.35.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, if a poison message missing queue information ends up in the SF
> queue, the broker logs an error, like:
> AMQ222110: no queue IDs defined...
> but the message remains in the queue, with the result that the bridge
> continuously reconnects, encounters the failure, then evicts the bridge
> consumer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
