[
https://issues.apache.org/jira/browse/ARTEMIS-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic resolved ARTEMIS-4357.
--------------------------------------
Resolution: Fixed
> Replace Logger.unableToFindTargetQueue (LoggerID 222188) by a logger.debug
> --------------------------------------------------------------------------
>
> Key: ARTEMIS-4357
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4357
> Project: ActiveMQ Artemis
> Issue Type: Task
> Affects Versions: 2.29.0
> Reporter: Clebert Suconic
> Priority: Major
> Fix For: 2.30.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When retry is called on a queue that is not a DLQ, or if the messages don't
> have any source queue, you will see this very verbose output:
> 608871 [main] 02:13:23,669 WARN [org.apache.activemq.artemis.core.server]
> AMQ222188: Unable to find target queue for node null
> 608872 [main] 02:13:23,669 WARN [org.apache.activemq.artemis.core.server]
> AMQ222188: Unable to find target queue for node null
> 608873 [main] 02:13:23,669 WARN [org.apache.activemq.artemis.core.server]
> AMQ222188: Unable to find target queue for node null
> 608874 [main] 02:13:23,669 WARN [org.apache.activemq.artemis.core.server]
> AMQ222188: Unable to find target queue for node null
> 608875 [main] 02:13:23,669 WARN [org.apache.activemq.artemis.core.server]
> AMQ222188: Unable to find target queue for node null
> 608876 [main] 02:13:23,669 WARN [org.apache.activemq.artemis.core.server]
> AMQ222188: Unable to find target queue for node null
> 608877 [main] 02:13:23,669 WARN [org.apache.activemq.artemis.core.server]
> AMQ222188: Unable to find target queue for node null
> 608878 [main] 02:13:23,669 WARN [org.apache.activemq.artemis.core.server]
> AMQ222188: Unable to find target queue for node null
> 608879 [main] 02:13:23,669 WARN [org.apache.activemq.artemis.core.server]
> AMQ222188: Unable to find target queue for node null
> 608880 [main] 02:13:23,669 WARN [org.apache.activemq.artemis.core.server]
> AMQ222188: Unable to find target queue for node null
> We should instead be using a logger.debug for such thing.
> The same loggerID (222188) might still be used by moveSNF or other method,
> but the retry operation shouldn't use it any longer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
