james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Rusin (JIRA)" <server-...@james.apache.org>
Subject [jira] [Reopened] (JAMES-1429) FileMailQueue looks like it does not survive James restart
Date Tue, 14 Aug 2012 11:50:37 GMT

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

Andrzej Rusin reopened JAMES-1429:


Thanks for the atempt to fix it.

Let me summarize how it behaves after your fix (I am experimenting on 1 email in the queue
for clarity):

0. I compose an email and let it attempt delivery once (while simulating undeliverability
conditions). When it attempts and stores back into outgoing, I restart James
1. After the restart the email is retried IMMEDIATELY, while I think it should wait a bit
for it's retry time.
2. When the attempt is unsuccessful, the log says:
Storing message Mail1344941530953-04fcaffc-b060-4901-bb6d-d3c99f3a8961 into outgoing after
1 retries
3. The retry times are configured 5, 10, 45 minutes, 2, 3, 6... hours. So theoretically, after
the 1st retry, it should wait 10 minutes and retry again. However, it does not. It's already
55 minutes after point 1 and no retry.

BTW, it's very easy to simulate undeliverability conditions by misconfiguring the gateway
for RemoteDelivery.
> FileMailQueue looks like it does not survive James restart
> ----------------------------------------------------------
>                 Key: JAMES-1429
>                 URL: https://issues.apache.org/jira/browse/JAMES-1429
>             Project: JAMES Server
>          Issue Type: Bug
>          Components: Queue
>    Affects Versions: 3.0-beta3
>         Environment: Java 6 on Linux
>            Reporter: Andrzej Rusin
>            Assignee: Eric Charles
>             Fix For: 3.0-beta5
> When I restart James (eg. for emergency reconfiguration), the mails in the queue (for
example ca 2500 of them) look like they are stuck.
> The mails in the queue were mostly retries (and it was emergency) - if that matters.
> I believe that after the restart they are not delivered, not retried, not deleted at
> BTW, we use FileMailQueue becasue the ActiveMQ based queue tended to hang for us for
no good reason.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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

View raw message