NNTP-JS doesn't handle network errors as well as the old C++ module
Categories
(MailNews Core :: Networking: NNTP, defect)
Tracking
(Not tracked)
People
(Reporter: b5, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36
Steps to reproduce:
This was discussed in de.comm.software.mozilla.mailnews.
A user fetches news messages at startup, but then afterwards only on demand, that is, option "check for new messages every ..." is not checked.
When entering a newsgroup, new messages are fetched from the server. Manually fetching messages from the server manually straight afterwards shouldn't yield any more new messages. The user reports that with debugging turned on they see this:
mailnews.nntp:
error { target: TCPSocket, isTrusted: true, name: "NetworkError",
message: "Network", errorCode: 2152398868, srcElement: TCPSocket,
currentTarget: TCPSocket, eventPhase: 2, bubbles: false, cancelable:
false, … }
NetworkError Network 2152398868 NntpClient.jsm:225:18
mailnews.nntp: Done with status=2152398868 NntpClient.jsm:848:18
mailnews.nntp: Connection closed. NntpClient.jsm:233:18
This error is:
Value 0x804B0014 (2152398868)
Name NS_ERROR_NET_RESET
Pressing F5 seconds later in most cases fetches new messages successfully.
The user further reports that the behaviour is better when switching to the old C++ module, that is, opening a NG folder always seems to fetch messages successfully and a subsequent F5 yields no new messages.
Possibly the C++ module treated this error differently of retried immediately. It's also questionable whether the error should be shown in the UI.
In summary, the user prefers the behaviour of the C++ module.
Description
•