Just an update on this issue. Last week I was able to release a new version of
our software to all of our customers and I included some extra logging for this
issue. Yesterday we had a customer report the problem. Here’s what I found.
First, a bit about the process that I’ve seen freeze the most often. It is
simply a background process that runs on the server. It checks to see if some
work needs to be done and then delays itself for 60 ticks. Then it checks
again. When work does need to be done it is spun off in another process, so
this process doesn’t do a lot. It hasn’t changed much since implemented in 4D
2004.
Based on the logging, I can see that the last line of code run was:
DELAY PROCESS(Current process;60*1)
That line of code ran at 8:15:37 AM yesterday. We found out about the problem
at 1:01 PM, so it had been hung for several hours.
Now that I have some logging I’m hoping to see a few more instance to see
whether they all point to the same thing. In the mean time, does this line up
with what anyone else is seeing?
--
Cannon.Smith
Synergy Farm Solutions Inc.
Hill Spring, AB Canada
403-626-3236
<[email protected]>
<www.synergyfarmsolutions.com>
> On Sep 13, 2017, at 7:58 PM, Jeffrey Kain via 4D_Tech <[email protected]>
> wrote:
>
> Just saw this happen to our production server tonight. We have a stored
> procedure that simply calls New Log File every few minutes. About an hour
> ago it just stopped working. The process is still there in the process list,
> and nothing else seems wrong with the server, but this very simple stored
> procedure just stopped working.
>
> I've never seen this happen in 4D before.
>
> 4D v16.2, Windows Server 2012, 64-bit
>
**********************************************************************
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]
**********************************************************************
