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 "Eike Kettner (JIRA)" <se...@james.apache.org> on 2013/01/03 12:26:12 UTC

[jira] [Created] (JAMES-1463) Issues in FileMailQueue

Eike Kettner created JAMES-1463:
-----------------------------------

             Summary: Issues in FileMailQueue
                 Key: JAMES-1463
                 URL: https://issues.apache.org/jira/browse/JAMES-1463
             Project: James Server
          Issue Type: Bug
          Components: Queue
            Reporter: Eike Kettner


I found some issues in FileMailQueue. In JAMES-1429 the problem in the `init()` method was solved. I think the remaining problems described there could be related to the first of these two:

* in `enQueue()`, the NEXT_DELIVERY date is set into the mail _after_ it has already been written to disk. So after a restart, the mails are put into the queue without taking the NEXT_DELIVERY into account. This would result in delivering them immediately, if I understand correctly.
* in `deQueue()` l.289, the file item is deleted, but the `keyMappings` cache is not updated. This breaks the management methods (clear/flush/browse) and the cache will grow infinitely.

I'll attach a patch for these two.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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