Posted by Brian Levantine on February 11, 2004 at 15:49:19:
In Reply to: Comet Anywhere and dropped communications posted by Jean-Pierre DUBREUIL on February 11, 2004 at 11:38:48:
Hello Jean-Pierre. Generally, this kind of problem is due to unreliable TCP/IP behavior - usually a poor ISP connection. When Comet's session connection manager (COSC) hasn't recieved a packet of data from a session for about 30 seconds, it sends a poll to the session and then waits another 30 seconds for a reply. It will attempt this poll-reply sequence 3 times. If after sending the 3 polls, COSC still doesn't get a response, it will attempt to disconnect the session. Depending on the nature of the problem, the session could remain locked up for a few minutes. You can learn more about the nature of the problem by examining the "Startup Details" log on the CometAnywhere host computer. If you start Comet with a "/LOG" command line parameter, COSC will copy all log events to a disk file named (YourProfile).log. If you can enable this feature I'd be happy to take a look at the log file for you next time this happens. You should also send me more detailed information that describes the system topology - especially where CometAnywhere is involved.