[ http://issues.apache.org/jira/browse/JAMES-603?page=all ]
Stefano Bagnara resolved JAMES-603.
-----------------------------------
Resolution: Fixed
I just tested this in production and everything seems ok.
> 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
> Assigned To: Noel J. Bergman
> Priority: Blocker
> Fix For: 2.3.0rc3
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]