[
https://issues.apache.org/jira/browse/ARTEMIS-4924?focusedWorklogId=927139&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-927139
]
ASF GitHub Bot logged work on ARTEMIS-4924:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 24/Jul/24 03:08
Start Date: 24/Jul/24 03:08
Worklog Time Spent: 10m
Work Description: gaohoward commented on PR #5091:
URL:
https://github.com/apache/activemq-artemis/pull/5091#issuecomment-2246775844
> I'm running the whole test suite now. if it's good it LGTM.
>
> @gtully let me know what you think... I will post the results for the test
suite here. We should probably merge this before the release if it's all good.
Thanks @clebertsuconic
Issue Time Tracking
-------------------
Worklog Id: (was: 927139)
Time Spent: 50m (was: 40m)
> 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: 50m
> 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
