You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2016/10/28 10:03:59 UTC
[jira] [Updated] (QPID-7473) [Java Broker] Asynchronous message
recoverer should always delete orphan messages from the store
[ https://issues.apache.org/jira/browse/QPID-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey updated QPID-7473:
------------------------------
Status: Reviewable (was: In Progress)
> [Java Broker] Asynchronous message recoverer should always delete orphan messages from the store
> ------------------------------------------------------------------------------------------------
>
> Key: QPID-7473
> URL: https://issues.apache.org/jira/browse/QPID-7473
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1
> Reporter: Alex Rudyy
> Assignee: Rob Godfrey
> Fix For: qpid-java-6.2
>
>
> Asynchronous message recoverer can leave orphan messages in store in the following scenario:
> * transient messages for non-durable queues were flown to disk due reaching 'flow to disk' memory threshold
> * broker is restarted with flown to disk transient messages and there is no durable queue on the virtual host
> Asynchronous message recoverer performs orphan messages deletion only as part of the last QueueRecoveringTask. Thus, if there is no persistent queue on the virtual host, the orphan message deletion will not be triggered
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org