You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/07/16 08:40:00 UTC
[jira] [Work logged] (ARTEMIS-4924) Do not allow sending messages directly to store-and-forward queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4924?focusedWorklogId=926075&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-926075 ]
ASF GitHub Bot logged work on ARTEMIS-4924:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jul/24 08:39
Start Date: 16/Jul/24 08:39
Worklog Time Spent: 10m
Work Description: gaohoward opened a new pull request, #5091:
URL: https://github.com/apache/activemq-artemis/pull/5091
(no comment)
Issue Time Tracking
-------------------
Worklog Id: (was: 926075)
Remaining Estimate: 0h
Time Spent: 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: 10m
> 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-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact