You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2019/08/02 07:12:00 UTC

[jira] [Resolved] (JAMES-2757) rabbitmq MailQueueView.isPresent is never called

     [ https://issues.apache.org/jira/browse/JAMES-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tellier Benoit resolved JAMES-2757.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.4.0

> rabbitmq MailQueueView.isPresent is never called
> ------------------------------------------------
>
>                 Key: JAMES-2757
>                 URL: https://issues.apache.org/jira/browse/JAMES-2757
>             Project: James Server
>          Issue Type: Improvement
>          Components: Queue, rabbitmq
>            Reporter: Matthieu Baechler
>            Priority: Major
>             Fix For: 3.4.0
>
>
> As far as I know, the design of rabbitmq MailQueue is the following:
> On Enqueue:
> 1. put the raw message in a blobstore
> 2. put the reference to it into rabbitmq
> 3. put some metadata about it into cassandra
> On Delete:
> 1. use cassandra to browse messages in the queue and remove the ones that match the query
> On Dequeue:
> 1. take the next message from rabbit
> 2. check that the message is not deleted by calling cassandra MailQueueView.isPresent
> On browse:
> 1. use cassandra MailQueueView to list not yet deleted messages
> It looks like we don't check that the message is not deleted on dequeue.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org