[
https://issues.apache.org/jira/browse/JAMES-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434124#comment-13434124
]
Andrzej Rusin edited comment on JAMES-1429 at 8/15/12 12:51 AM:
----------------------------------------------------------------
Eric,
For what it's worth, it looks like after the fix it is not retrying AT ALL with
the regular schedule of remote delivery.
To be clear, it retries only on James restarts, but not according to the
configured retry intervals.
Wonder why.
was (Author: arusin):
Eric,
For what it's worth, it looks like after the fix it is not retrying AT ALL.
Wonder why.
> 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 all.
> 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: [email protected]
For additional commands, e-mail: [email protected]
