179818 - "blocked" when reading news, while posting

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking: NNTP, defect)

Description

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

"blocked" when reading news, while posting.

to reproduce:

1) read news in n.p.m.mail-news
2) reply to a post.
3) while the reply is posting, try to read another article in n.p.m.mail-news
4) unable to read the article until the post succeeded

we should be able to do this, right?  at worst, we'd see the connection is busy 
and open a new connection.

Comment 1

[David :Bienvenu]

yes, I would have thought we'd open a new connection -
nsNntpIncomingServer::GetNntpConnection() basically blows off the max number of
connections, as near as I can tell, and will create new connections. It creates
the new protocol object, anyway. I wonder if something else is blocking us?

Comment 2

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

sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.

Comment 3

[Serge Gautherie (:sgautherie)]

Filter on "Nobody_NScomTLD_20080620"

Comment 4

[Wayne Mery (:wsmwk)]

tony can you reproduce?

Comment 5

[Tony Mechelynck [:tonymec]]

(In reply to comment #4)
> tony can you reproduce?

I don't know. Usually my newsposts go so fast that I can't be sure to read a new post "after" triggering the posting of a reply to a previous one but "before" it has succeeded -- except, of course, if the modem is down, but in that case the attempted "read" would, if anything, give an error.

What I remember seeing is that if the modem has been disconnected from the other side, an attempted read after reconnect will only succeed after offline-online; this is bug 465204.

Comment 6

[Joshua Cranmer [:jcranmer]]

So, via my testing with tc and wireshark, I think this doesn't work.
I told tc to delay packets by 10s (!).
Wireshark indicates:
164.664230	128.61.91.23	216.196.97.169	NNTP	Request: POST
164.727529	216.196.97.169	128.61.91.23	NNTP	Response: 340 send article
166.613501	128.61.91.23	216.196.97.169	NNTP	Request: ARTICLE 5226
166.762861      216.196.97.169  128.61.91.23    NNTP    Response: 220 [article]
174.729107	128.61.91.23	216.196.97.169	NNTP	Request: [posting]

Given that the timestamps indicate the post-packet delay, this indicates that the program did not wait 10 seconds for the response to come back before requesting the article.

In short... WFM.