james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman (JIRA)" <server-...@james.apache.org>
Subject [jira] Updated: (JAMES-603) Outgoing spooling stuck over old mails when more than 1000 old mails are present in outgoing.
Date Mon, 04 Sep 2006 19:08:23 GMT
     [ http://issues.apache.org/jira/browse/JAMES-603?page=all ]

Noel J. Bergman updated JAMES-603:
----------------------------------

    Attachment: spool-fix.patch

Attached is a first pass at an attempt to fix.  I have reviewed it, and provided it directly
to Stefano to review and try.

I have NOT tried it on my system, yet, and won't put it on my production server for a while
because I am trying to keep the current process going to verify the lack of memory leaks.
 But I want to get this out for review ASAP, before I have time to do some bench testing.

> Outgoing spooling stuck over old mails when more than 1000 old mails are present in outgoing.
> ---------------------------------------------------------------------------------------------
>
>                 Key: JAMES-603
>                 URL: http://issues.apache.org/jira/browse/JAMES-603
>             Project: James
>          Issue Type: Bug
>          Components: Remote Delivery, SpoolManager & Processors
>    Affects Versions: 2.3.0rc2
>            Reporter: Stefano Bagnara
>            Priority: Blocker
>             Fix For: 2.3.0
>
>         Attachments: spool-fix.patch
>
>
> scenario:
> remote delivery has 6 hours for the third delaytime
> insert into the outgoing spool 1000 messages with a last_updated 5 hours ago and error_message
3
> start james
> send a new message
> the first remote delivery thread is stuck in the main accept method because getNextPendingMessage
ALWAYS return a new pending message but none of them is ready to be processed. The bad news
is that after it finish the 1000 messages from pendingMessages it simply restart the loadPendingMessages
and try them again, without waiting.
> So 100% CPU used until we are able to spool the 1000 "old" messages and then our james
will return to normality.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.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


Mime
View raw message