[ 
https://issues.apache.org/jira/browse/ARTEMIS-4924?focusedWorklogId=930987&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-930987
 ]

ASF GitHub Bot logged work on ARTEMIS-4924:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Aug/24 14:43
            Start Date: 20/Aug/24 14:43
    Worklog Time Spent: 10m 
      Work Description: gtully commented on PR #5091:
URL: 
https://github.com/apache/activemq-artemis/pull/5091#issuecomment-2299036859

   I think the commit message needs to be  updated to better reflect what it is 
now doing.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 930987)
    Time Spent: 2h  (was: 1h 50m)

> 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: 2h
>  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


Reply via email to