|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
08/Sep/06 05:12 PM
|
|
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.
|
|
Description
|
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.
|
Show » |
| No work has yet been logged on this issue.
|
|
Bug
Closed
Blocker
Outgoing spooling stuck over old mails when more than 1000 old mails are present in outgoing.
