Manual get messages can cause process collision: "This folder is being processed. Please wait until processing is complete to get messages." (15 pop accounts)
Categories
(MailNews Core :: Networking: POP, defect)
Tracking
(Not tracked)
People
(Reporter: dannyfox, Unassigned)
References
(Depends on 1 open bug)
Details
Reporter | ||
Comment 1•12 years ago
|
||
Updated•12 years ago
|
Comment 3•11 years ago
|
||
Reporter | ||
Comment 4•11 years ago
|
||
Comment 5•11 years ago
|
||
Reporter | ||
Comment 6•11 years ago
|
||
Comment 7•11 years ago
|
||
Reporter | ||
Comment 8•11 years ago
|
||
Reporter | ||
Comment 9•11 years ago
|
||
Comment 10•11 years ago
|
||
Comment 11•11 years ago
|
||
Reporter | ||
Comment 12•11 years ago
|
||
Reporter | ||
Comment 13•11 years ago
|
||
Comment 14•11 years ago
|
||
Comment 15•11 years ago
|
||
Comment 16•11 years ago
|
||
Comment 18•11 years ago
|
||
Reporter | ||
Comment 19•11 years ago
|
||
Comment 20•10 years ago
|
||
Reporter | ||
Comment 21•10 years ago
|
||
Comment 22•10 years ago
|
||
Reporter | ||
Comment 23•2 years ago
|
||
Cross-posted from Bug 707933...
Today I updated to TB 102.0.3 Release and re-enabled my GET MESSAGES button configuration. This bug still occurs.
I'm getting the occasional popup warning that certain accounts are "busy". Happened when I clicked GET MESSAGES first time and the timed fetches started too. In fact, for the first time I had two popups simultaneously -- one immediately on top of the other -- as the two accounts competed for attention, and a total of three popups altogether (out of ten accounts actively polled on this machine).
Comment 24•8 days ago
|
||
Dan do you still see this problem when using version 128?
If it is gone then this will have been solved by bug 1847137
Reporter | ||
Comment 25•4 days ago
|
||
Sorry, I'm not running v128. However we are running the latest v115 and it STILL occurs there very regularly.
As for the fix in Bug 1847137:
That bug is a little different than this one, because the errors repeatedly occur on their own ("spontaneously", I've said in my reports) when two timed GETMAIL operations collide since they happen to run at the same time. In my case I have rarely (but not never) had it happen spontaneously. But every day, manual collisions still occur if an automatic (timed) GETMAIL or GET ALL MAIL happens to be silently in progress when I manually trigger a GET ALL MAIL request and one of the fetches then collides with the automatic fetch already in progress. (I see the guys have stated that v115esr is affected but its status is "wontfix".)
Comment 26•4 days ago
|
||
Thank you for reminding that this can still happen with manual operations.
Description
•