226989 - getting a lot of "failed creating protocol instance to play queued"

Status: RESOLVED FIXED

(MailNews Core :: Networking: IMAP, defect)

Description

[Henrik Gemal]

I see a lot of these in my imap protocol log:

failed creating protocol instance to play queued
url:imap://[e-mail]:143/folderstatus>/Drafts

Mailclient setup:
5 IMAP accounts
4 of them are checked every 10 min
1 of them are checked every 1 min

4 NEWS accounts
all 4 of them are checked every 10 min

I can email the protocol log since I dont like attaching it. it contains
sensistive info

Comment 1

[David :Bienvenu]

is anything going wrong? That's a diagnostic (like the rest of the logging info)
that helps tell what's going on. It's not a bug in and of itself.

Comment 2

[Henrik Gemal]

it bug is about selecting messages and they dont show. it says loading message
and nothing happens. perhaps it's caused by having to many imap status checks? I
can email you a imap log if you want.

Comment 3

[David :Bienvenu]

yes, please, e-mail me a log. That log message is an indication that you've
already got 5 connections going on the server (or whatever your max cached
connections is) and they probably are doing STATUS. However, that shouldn't
cause a problem in and of itself because when each url finishes, it tries to run
the remaining queued urls. A problem would occur if for some reason a url is
queued but never gets to run. How many folders do you have getting checked? It
would be better if those checks were chained instead of queued all at once, but
I haven't done that yet.

Comment 4

[David :Bienvenu]

Attachment: proposed fix

this fixes the two problems I saw in Henrik's log - the first is a general
problem - we were doing STATUS on the root folder, if you check all folders for
new mail, and we were not parsing the STATUS mailboxname response correctly.
Henrik's server was returning the folder name as a string literal, which we
didn't parse correctly at all. So I fixed the status parsing code to just treat
the mailbox name as a string, as the RFC says - not sure where the initial
confusion about the syntax of the STATUS response came from, me or Kevin, but
it was long long ago. I also fixed the variable name to be clear that the
folder was not always aRootFolder, because the method is recursive.

Comment 5

[(not reading, please use [e-mail] instead)]

Comment on attachment 136596 [details] [diff] [review]
proposed fix

r/a=sspitzer for 1.6b, once you get sr=mscott

Comment 6

[David :Bienvenu]

fix for problems shown in log  checked in - please try tomorrow's build. If you
still have problems, can you e-mail me a new protocol log?

Comment 7

[David :Bienvenu]

Attachment: potential fix for negative unread message counts