james-server-dev mailing list archives

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

    [ https://issues.apache.org/jira/browse/JAMES-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434139#comment-13434139

Eric Charles commented on JAMES-1429:

Andrzej, I futher debugged and the file queue seems ok, the issue is not there.

Let me explain

1. Configuring a bad remote server is not that trivial. Something your socket simply hangs
for a the default connectionTimeout  (6000ms), which makes the remote delivery waiting long.
To really have a delivery failure, I had to remove my ethernet cable

2. Once the failure occur, i had configured the delayTime such as shown in the mailetcontainer-template,
with multiple delayTime tags, which is not how the current code expect. in fact, it excepts
something like <delayTime>5000, 10000, 500000</delayTime> where the delay is expressed
in ms

I will fix template and documentation  for remotedelivery, but here, it retries correctly
after a restart.
> 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