On Sep 8, 2017, at 5:05 PM, Cannon Smith via 4D_Tech <[email protected]> wrote: > > I’ve seen something odd since upgrading our customers to v16.1 a few months > ago. This is on 64-bit server, both platforms. There are a few background > processes that continually run on the servers, waking up every few seconds to > see if there is work to be done. This has worked without problem for a decade > now, but starting with v16.1 we occasionally have a process the just sort of > quits. > > By occasionally, I mean maybe once in 2-3 months per server. Little enough > that I didn’t pay much attention at first—just relaunched the server. But > cumulatively (across all servers) it has happened probably 20-30 times in the > last few months. > > By the process sort of quitting, I mean that the tasks it is supposed to take > care of just stop getting taken care of. The activity monitor shows the > process is still there and nothing I have noticed seems out of the ordinary. > It’s like the code just quit executing in that process.
This was happening in a system I upgraded to v16, relatively often. I never really narrowed down the cause, but after going through the code that executed, some rewriting, and explicitly handling locked records (i.e. making sure a record was loaded read-write before modifying and saving), the problem went away. Jim Crate ********************************************************************** 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] **********************************************************************
