I _could_ try that. But my turn around time to send a new build to customers is measured in months. And if I only try this with one customer’s server, it may not happen for weeks. How would I know if it solved it?
The trouble with this particular bug is that it has been very hard to reproduce. This is the first time I even have an idea of what line of code may be causing it. And it is only the first time I’ve been able to log it. I’ll have to log it a few more times to see if it is always DELAY PROCESS. Also, I’d rather have the bug figured out and fixed, not worked around. This method (and similar ones where I’ve seen this issue) have been running solid with basically no code changes for over a decade now. Tweaking it like that as a workaround, even if it worked, would keep me nervous for the next decade! -- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 <can...@synergyfarmsolutions.com> <www.synergyfarmsolutions.com> > On Oct 18, 2017, at 5:17 PM, Tim Nevels via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > So you are running this process every 1 second? Here’s a crazy idea: > > What if there is some strange timing issue that screws up the 1 second > interval. Something takes a bit to long on the server and the cooperative > multiprocessing system get hung up for just a bit longer than normal. So it > misses the next 1 second interval. > > Could you change the interval to 5 seconds? Give it some “breathing room” to > make sure it goes deeply asleep before it is awakened again. > ********************************************************************** 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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
