[ARTEMIS-4357] Replace Logger.unableToFindTargetQueue (LoggerID 222188) by a logger.debug

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.29.0
• Fix Version/s: 2.30.0
• Assignee: Unassigned
• Reporter: Clebert Suconic
• Created: 10/Jul/23 14:58
• Updated: 21/Jul/23 13:31
• Resolved: 10/Jul/23 18:32

Description

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.

Issue Links

• links to: GitHub Pull Request #4547