Closed
Bug 65975
Opened 24 years ago
Closed 24 years ago
News: opening multiple connections and not closing them for particular server
Categories
(MailNews Core :: Networking: NNTP, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: Bienvenu, Assigned: Bienvenu)
References
Details
Attachments
(5 files)
A user has reported that for one particular news server, we're opening a
connection per news message read, and not closing any of them down, so he runs
out of connections quickly. I'll attach a protocol log when I can get one. The
users' e-mail address is gord.mcfee@sympatico.ca
QA Contact: esther → stephend
Comment 1•24 years ago
|
||
Some people on IRC were having this problem with n.p.m.*
Assignee | ||
Comment 2•24 years ago
|
||
Did they see it on news.mozilla.org, or on some other server where those groups
are replicated?
Assignee | ||
Comment 3•24 years ago
|
||
Assignee | ||
Comment 4•24 years ago
|
||
I believe the problem here is that we're always opening a new connection for
every news posting you make, and never cleaning up that connection. The fix is
to look in the connection cache for a connection to use when posting a news
message. We should look at fixing the news protocol state machine to not allow
more than N open connections (i.e., closing connections instead of leaving them
in the cache if the cache is full).
Status: NEW → ASSIGNED
Comment 6•24 years ago
|
||
r=sspitzer
check that bad boy in.
http://bugzilla.mozilla.org/show_bug.cgi?id=66150 logged to track the other
issue you raised.
Comment 7•24 years ago
|
||
(bienvenu: news.mozilla.org, if it still matters)
Assignee | ||
Comment 8•24 years ago
|
||
hey, Scott, can I get an sr= when you get a chance? thanks!
Comment 9•24 years ago
|
||
sr=mscott
Assignee | ||
Comment 10•24 years ago
|
||
fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Bienvenu - can I verify this with some more NTTP log fun? :-) If so, tell me
what I'm looking for or not looking for, and I'll check this out. Thanks.
Assignee | ||
Comment 12•24 years ago
|
||
yes, you'll be looking for the absence of new connections getting made for each
posting - new connections show up in the log as the greeting response from the
server, usually.
You can also use netstat to see how many open connections you have to the news
server. You should really only have one.
Assignee | ||
Comment 14•24 years ago
|
||
Stephen, I think this bug is about doing news postings, not so much reading
messages as I originally thought. So you should generate a log of a session when
you post several news messages.
notice the 0[2f3fd0]: Receiving: 400 Too_Many_Connections
error. I got this on my 3rd attempt at posting, it never went through. Windows
2000, build 2001012205.
Assignee | ||
Comment 18•24 years ago
|
||
Stephen, my fix won't show up until tomorrow's build.
arrgg... ;-) I hate it when that happens.
I apologize for my NNTP log reading not being up to par, but here's what I
found. I'll attach a logfile, for Win32. Also, when I opened up netstat, I
found it wouldn't update in real time, and by the time it displayed my NNTP
listening and receiving ports, it was as follows:
stephend:3044 secnews1.mcom.com:nnttp (I did a netstat -n and it was indeed
port 119)
stephend:3055 secnews1.mcom.com:nntp (119)
Assignee | ||
Comment 22•24 years ago
|
||
Looks OK - you'll notice that in yesterday's build, before each post, there was
a server greeting:
200 secnews.netscape.com Netscape-Collabra/3.52 03615 NNRP ready (posting ok).
this means we made a new connection to the news server.
In today's log, there is *not* a server greeting response before each post.
Thanks for the clarification David, I'll check Mac and Linux now.
VERIFIED on Windows NT 4.0, Build 1-23-04
, Mac 2001-01-23-11. I'll mark this VERIFIED when I figure out the Linux log
file stuff ;-).
VERIFIED on Linux, build 2001012506.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•