[
https://issues.apache.org/jira/browse/JAMES-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434067#comment-13434067
]
Andrzej Rusin commented on JAMES-1429:
--------------------------------------
Eric,
Maybe I was not clear enough from the beginning, but I always meant the
'outgoing' use case, basically the queue of emails being attempted to send out
with RemoteDelivery and their retries. This was also the case in the original
issue report.
So, your original fix made some difference, that the emails now ARE retried one
time instead of zero after james restart, in the context of what you call
'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 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]
