Re: Comet time outs


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Grant Foraker on January 07, 2019 at 10:21:20: Uploaded files: 5

In Reply to: Comet time outs posted by Grant Foraker on December 27, 2018 at 07:06:34:

Retro'd from 516 to 512 to see what that might do on the time out problem. As expected, the 30 second delay when stopping and restarting Comet came back. There's nothing in the release notes for 513-516 that this was fixed but it went away ???

Left Comet (T00) running after the change (Saturday 01/05) at "ENTER PASSWORD".

This is came from the CFAM log. Couldn't find any other log postings.
-------------------------------------------------------------
01/06/2019
11:32:39 The virtual circuit was reset by the remote side.
11:32:39 Connection Abandonned
-------------------------------------------------------------
This morning typed in password and got the READY screen with no JPG. This only happens occasionally.

Ran an old QCRT program. OK.

Tried to run a WDL menu program. This is the usual first place things go bad.

Closed Comet but cfilesrv did not stop. Stopped it with Task Manager.

Looked in CATOOLS, both your JPG and my DLL were zero byes.

I'm going to switch to 517 tonight. At least, to get some of the in between changes back.

PS: no "nn" in Abandonned


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

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

Comments:

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 ] [ Signature.net Forum ]