[
https://issues.apache.org/jira/browse/QPID-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie resolved QPID-1049.
----------------------------------
Resolution: Fixed
Assignee: Martin Ritchie
Refactoring to TopicExchange removed the warn log statements.
> Unnecessary WARN level logging in DestWildExchange
> --------------------------------------------------
>
> Key: QPID-1049
> URL: https://issues.apache.org/jira/browse/QPID-1049
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: M2, M2.1
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Priority: Minor
> Fix For: M3
>
>
> Summary:
> Currently the route method outputs the following warnings if there are no
> matching queues for the give 'routingKey'. Whilst these messages are useful
> they should not be WARN level.
> _logger.warn("No queues found for routing key " + routingKey);
> _logger.warn("Routing map contains: " + _bindingKey2queues);
> Work around, adding the following to log4j will prevent this output.
> <!-- Prevent 'No queues' messages logged at WARN on every publish where
> there is no queue on that topic -->
> <category name="org.apache.qpid.server.exchange.DestWildExchange">
> <priority value="OFF"/>
> </category>
> Doing this will prevent the other logging in the file.
> Debug: Queue Registration
> Error: An Exception creating the MBean.
> Perhaps setting priority to error would at least still allow the MBean
> creation exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
