[
https://issues.apache.org/jira/browse/ARTEMIS-4924?focusedWorklogId=926981&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-926981
]
ASF GitHub Bot logged work on ARTEMIS-4924:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jul/24 02:15
Start Date: 23/Jul/24 02:15
Worklog Time Spent: 10m
Work Description: gaohoward commented on PR #5091:
URL:
https://github.com/apache/activemq-artemis/pull/5091#issuecomment-2244120494
@gtully @jbertram I've upated the PR. Now when a cluster connection is
activated, a Role is added so that when security is enabled any client will be
denied of sending messages to store and forward queues. When security is
disabled, or user overrides the role in security settings, messages are sent to
snf queue will be moved to DLQ during delivery time.
Issue Time Tracking
-------------------
Worklog Id: (was: 926981)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
