Re: Keep Alive Packet

[ Follow Ups ] [ Post Followup ] [ Forum ]

Posted by Justin Guerber on April 11, 2024 at 13:10:11:

In Reply to: Keep Alive Packet posted by Robert G Laurin on April 04, 2024 at 11:56:08:

These kinds of issues are very hard to debug, because there are so many factors that can cause the issue, and we cannot recreate the environment to test what exactly is going wrong.

From the log entries you posted, there are a few things that could be happening. The socket connections get closed when they read an incoming packet with 0 bytes of data. This is an underlying mechanism for most socket code in Comet. If there was an intermittent network issue, or possibly a content filter/antivirus on the network blocking content, that could cause a 0 byte packet to be sent, which would close the connection prematurely. It could also be a loose network wire, or moving from one wifi AP to another. Or a failing hub/switch.

This log entry

04/03/24 09:53:43 (2924): (28003605):: CSocketServer::OnConnectionReset: The specified network name is no longer available.

appears to have been caused when the socket was reset because of a windows networking error. This could be from an underlying TCP layer reset, or again could be Antivirus blocking content. This also appears to be an issue with windows shares having to do with SMB (server message block), here's a link to one page I found about how to resolve this issue.

As always, I'm happy to look through log files to try and diagnose what's going wrong! With just descriptions of behavior, it's very hard to diagnose.

Follow Ups:

Post a Followup



What is the name of the main Signature System's Product?  


Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):

Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.

[ Follow Ups ] [ Post Followup ] [ Forum ]