Re: Delay process bug

I would like to emphasize this. It’s likely processes delayed with DELAY PROCESS are woken up by some internal process that ends up getting stopped somehow. The bug is most likely not in DELAY PROCESS, but the internal process that (among many other things) checks the list of delayed processes

Re: Delay process bug

Just for the record I can confirm that I have a mac server with a stored procedure that works like beneath, where I have seen this freezing state. Repeat . Find potential things to do Do it if any . Delay Process(Current Process;60*60) // Delay 60 sec Until (stopCallFromOutside) This is a v15R5

Re: Delay process bug

Jeffrey Kain: > It seems like a big clue is that the 4D Server user interface stops updating > when this happens. Like the internal clock/heartbeat/metronome of 4D Server > just stops, and DELAY PROCESS comes along for the ride. Server might be a clue indeed. It happened only on the Server

Re: Delay process bug

It seems like a big clue is that the 4D Server user interface stops updating when this happens. Like the internal clock/heartbeat/metronome of 4D Server just stops, and DELAY PROCESS comes along for the ride. -- Jeffrey Kain jeffrey.k...@gmail.com > On Jun 18, 2018, at 8:36 PM, Justin Carr via

Re: Delay process bug

This is a new bug in version 16. Lots of experience it but nobody can reproduce it. > On Jun 18, 2018, at 5:02 PM, Chuck Miller via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > i use delay process for years with no issues, however, I do not think I ever > delay for more than 15 minutes.

Re: Delay process bug

i use delay process for years with no issues, however, I do not think I ever delay for more than 15 minutes. Chuck Chuck Miller Voice: (617) 739-0306 Informed Solutions, Inc. Fax: (617) 232-1064

Re: Delay process bug

I can’t answer this for Justin, but we have both kinds hitting this bug. Some are rather complicated methods that potentially do lots of things. But several are very simple—just a few lines of code to check whatever it needs to check and then go back to sleep. -- Cannon.Smith Synergy Farm

Re: Delay process bug

Our development server stopped updating its user interface today. Same symptoms as the DELAY PROCESS bug - the admin graphs like CPU usage stop, the list of connected users goes out of date, uptime calculations reflect the time the internal clock stopped. Normally we start getting alerts on

Re: Delay process bug

Justin, Yeah, after I responded to you I read Miyako's comment - and your reply. It's an incredibly frustrating place to be when you do everything right and the wrong thing still happens. Unlucky. I bet the bug is actually someplace else and is manifesting in this DELAY PROCESS bit. Which doesn't

Re: Delay process bug

On 18 Jun 2018, at 4:39 pm, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> wrote: > > Justin, > I do use DELAY PROCESS but as I said it's only for a minute or two. > And like I said maybe I've simply been lucky. As my business mentor used to > say, "sometimes it's better to be lucky than smart."

Re: Delay process bug

Justin, I do use DELAY PROCESS but as I said it's only for a minute or two. And like I said maybe I've simply been lucky. As my business mentor used to say, "sometimes it's better to be lucky than smart." On Sun, Jun 17, 2018 at 7:45 PM Justin Carr via 4D_Tech < 4d_tech@lists.4d.com> wrote: > On

Re: Delay process bug

Keisuke Miyako: > it's not that the DELAY P. has a problem resuming, > the problem manifests itself when the codes pauses a process that is already > in "delay" status. > a double resume is required to cancel a delay-double combo. That would be another bug then. Over here it was a simple loop

Re: Delay process bug

On 18 Jun 2018, at 1:31 pm, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> wrote: > > according to the bug description for ACI0098368 ("Delayed processes do not > wake up if paused/resumed while already delayed"), > > it's not that the DELAY P. has a problem resuming, > the problem

Re: Delay process bug

according to the bug description for ACI0098368 ("Delayed processes do not wake up if paused/resumed while already delayed"), it's not that the DELAY P. has a problem resuming, the problem manifests itself when the codes pauses a process that is already in "delay" status. a double resume is

Re: Delay process bug

On 16 Jun 2018, at 12:20 am, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> wrote: > > I have never had an issue with DELAY PROCESS. Maybe I'm lucky. I don't > think I've ever used it to delay something more than a matter of seconds, > though. It would never have occurred to me to DELAY PROCESS

Re: Delay process bug

I have never had an issue with DELAY PROCESS. Maybe I'm lucky. I don't think I've ever used it to delay something more than a matter of seconds, though. It would never have occurred to me to DELAY PROCESS for minutes or hours. If I have some process I only want one instance of, maybe processing

Re: Delay process bug

Bryan Green: > Actually, that's exactly what I meant -- short-term (5 minutes, 10 minutes, > etc.) kind of delay using DELAY PROCESS is more stable than something like 12 > hours, 1 day, etc. using DELAY PROCESS. If by "more stable" you mean "hangs only every few weeks" that may be right. I

Re: Delay process bug

> On Jun 13, 2018, at 14:28, Chuck Miller via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > What does that mean? If you have a cron job process running on server that > wakes every 5 minutes to check and launch other processes. Is that what you > consider short term scheduling? Actually, that's

Re: Delay process bug

What does that mean? If you have a cron job process running on server that wakes every 5 minutes to check and launch other processes. Is that what you consider short term scheduling? Regards Chuck

Re: Delay process bug

That happened to me once in an earlier version of 4D. Long story short, DELAY PROCESS is meant for short-term scheduling, not long-term process management. Even so, it’s good to know in advance. -- bag Sent from my mobile On Jun 12, 2018, at 13:57, Dennis, Neil via 4D_Tech

Re: Delay process bug

Hi Jim, Is there somehow PAUSE PROCESS/RESUME PROCESS involved? I don't know if this has something to do with our issue, but I'd like to share a change in behavior (bug?) between v15 (and older) and v16 (and later). Also struggling with a process not waking up after the delay time, I found

Re: Delay process bug

Cannon Smith: > We just released a new version of our software a week and a half ago. In this > version I added a palette window on the server which runs On Timer. I also > added code to most every background process which updates some information > every time it wakes up from a Delay Process

RE: Delay process bug

I also did some digging our servers are patched on a monthly bases and restarted. So usually restart is few days over the 24.74 days. We have only had one instance of the delay process bug. So most of the time, even if it is a 32 bit signed integer problem, we don't have an issue with the delay

Re: Delay process bug

I doublechecked the time the server was started until the last time the processes were delayed and it was actually 24.74 (2137700 seconds). The processes were delayed for 5 minutes. However, that time period + the delay is still 9,483,647 ms, or 2.63 hours, short of the 2147483647 max signed

RE: Delay process bug

> 32-bit long integer flips to negative, after 24 days. You might be on to something  Could pass this on to the 4D tech guys... there are several bugs already reported for this. Neil Privacy Disclaimer: This message contains confidential information and is intended only for the named

Re: Delay process bug

There have been enough reports that they know it happens on both macOS and Windows. Multiple reports indicate the processes can continue when RESUME PROCESS is called. In this case RESUME PROCESS would have worked, because when quitting the server, the processes started again because the

Re: Delay process bug

We just released a new version of our software a week and a half ago. In this version I added a palette window on the server which runs On Timer. I also added code to most every background process which updates some information every time it wakes up from a Delay Process call. The palette

Re: Delay process bug

22 days does sound suspicious; as if (no proof), the scheduler is testing if milliseconds "minus" process up-time is "greater than" delay time... such logic would break when milliseconds expressed in signed 32-bit long integer flips to negative, after 24 days. (milliseconds is counted since

RE: Delay process bug

> DELAY PROCESS never comes back Be sure to submit a bug with 4D when this happens. I submitted one and they said if it isn't reproducible they "can't" fix it. If there is enough complaining about it, I hope they would spend time digging into it and realize it is a problem even if it can't be

Re: Delay process bug

Our server (macOS 10.11, 4D 16.3 HF3 64-bit) hit this bug again last week after being up for about 22 days. There are 2 separate processes that run periodically, both at the same time stopped waking from DELAY PROCESS. The Server window also was not showing the 4D username in the user list,

Re: Delay process bug

> On 1/04/2018, at 7:00 am, Jeffrey Kain wrote: > So, the Delay Process bug hit two servers within an hour of each other this > morning, after months of not having the issue. It was weird that both of > them hit the bug this morning within a short period of time of each other. > This was on

Re: DELAY PROCESS bug

John DeSoi: > 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.

Re: DELAY PROCESS bug

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

RE: DELAY PROCESS bug

Drew Waddell: > 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

Re: DELAY PROCESS bug

After this discussion I ran a test server for several weeks before upgrading from 15.4 to 16.3 (Mac 64 bit). No problem running jobs on the server interleaved with DELAY PROCESS. After upgrading the production database to 16.3, a client running this same procedure regularly locks up. It seems

RE: DELAY PROCESS bug

@Cannon It's like Inception... I don't want to go down that path -Original Message- From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Cannon Smith via 4D_Tech Sent: Friday, January 05, 2018 1:44 PM To: 4D iNug Technical Cc: Cannon Smith Subject: Re: DELAY PROCESS bug

Re: DELAY PROCESS bug

Yeah, that's a pretty significant bug. Hopefully they fix it! I tried it on a Windows Server 2012R2 machine running 4D Remote, and did a ctrl-S over the DELAY PROCESS line and then minimized -- same thing. RESUME PROCESS did nothing. > On Jan 5, 2018, at 1:40 PM, Drew Waddell

Re: DELAY PROCESS bug

> 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. And then another process to watch the watch dog process in case it stops. And then another one to watch the one watching the watch dog. Etc. :-)

RE: DELAY PROCESS bug

I might chime in here as well: "Sometimes", under certain conditions, HIDE PROCESS behaves the same as DELAY PROCESS e.g. code should keep executing after HIDE PROCESS, but it gets "delayed" instead. I've not narrowed in down but we are certainly seeing this happen. Are these issues related?

RE: DELAY PROCESS bug

Technical Cc: Jeff Kain Subject: Re: DELAY PROCESS bug Hmmm... another issue with DELAY PROCESS. We have the issue in v16 where stored procedures that are delayed will sometimes never wake up. In our case, it's our mirror process. Sometimes the stored procedure just stops, forever delayed

Re: DELAY PROCESS bug

Hmmm... another issue with DELAY PROCESS. We have the issue in v16 where stored procedures that are delayed will sometimes never wake up. In our case, it's our mirror process. Sometimes the stored procedure just stops, forever delayed. It is possible to resume it by opening the Runtime

Re: DELAY PROCESS bug

Hi Drew, I wonder if this might be related to the Server Process Frozen issue lots of us have been experiencing. It sounds like the result is pretty much the same. -- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 > On Jan 5,