[
https://issues.apache.org/jira/browse/QPID-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176194#comment-16176194
]
Keith Wall commented on QPID-7913:
----------------------------------
One case we see this is where transient messages on non-durable queues have
been flowed to disk. If the Broker is restarted at that point, large numbers of
these messages are written to the log, which the user just needs to know to
ignore. The underlying issue is that transient messages and persistent
messages should be somehow separated within the store and the former not
broadcast over the HA replication network, but in the meantime if the user did
not drown in useless WARNs.
> [Java Broker] Improve message recovery logging
> ----------------------------------------------
>
> Key: QPID-7913
> URL: https://issues.apache.org/jira/browse/QPID-7913
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0, qpid-java-6.1, qpid-java-broker-7.0.0
> Reporter: Alex Rudyy
> Priority: Minor
> Fix For: qpid-java-broker-7.0.0
>
>
> Qpid broker message store recoverer generates a warning for every discarded
> message as below
> {noformat}
> WARN [VirtualHostNode-default-Config]
> (o.a.q.s.v.SynchronousMessageStoreRecoverer) - Message id 11800003 in log
> references queue with id de12d20b-bf6c-4d7b-a216-f613ee0635ae which is not in
> the configuration, entry will be discarded
> {noformat}
> Potentially, the logging can be improved to generate a single log entry per
> queue rather that per each message, where a number of discarded messages and
> their ids can be reported.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
