Bernd, Are you having this issue with the server, client, or both? I'm just seeing it with 4D Client. My new theory is that during a long delay 4D Server disconnects the client because there is no activity and 4D Server timeout (selector 13 for SET DATABASE PARAMETER) is reached. This may be wrong because I ran experiments yesterday and still could not reproduce the problem. But I changed the database setting in the dialog from 15 minutes to unlimited and the client did not hang last night as it has the last several.
I'm going to test setting this parameter locally for the execution process and see that happens. John DeSoi, Ph.D. > On Jan 8, 2018, at 1:39 AM, Bernd Fröhlich via 4D_Tech <[email protected]> > wrote: > >> That's not really a solution though, we'd have to write like a process >> watching that would have to make a call that process needed to be revived. > > Just make sure the watching process does not depend on using Delay Process > for itself. > > Since Delay Process sometimes just behaves like Pause Process, I decided to > use Pause Process instead and wake it from another process that uses a window > with a timer to do a Resume Process. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
