>
> Perhaps I am misunderstanding your question. Do you mean after a worker
> has been killed with KILL WORKER?
>
Clearly, I asked my question poorly as you and Julio both found my
question unclear in the same way. (Or perhaps it's just that it's unclear
to people who can speak Portuguese?) In
Julio,
Thanks for taking a stab at it. I should have been more clear, I mean when
workers are killed. I do this from within the worker to try and have an
orderly shutdown. Your reading of the docs is correct though. Workers are a
thread of execution, like any other process, but 4D has its own
On Oct 5, 2017, at 11:06 PM, David Adams via 4D_Tech <4d_tech@lists.4d.com>
wrote:
>
> * New process () / Execute on server () When they finish, they're dead.
> They're supposed to release file locks, record locks, etc. If you start a
> new copy of the process with the same name, it starts off
Well, documentation says Workers don’t die. You have to kill them, or quit 4D.
From 4D 16.2 Docs, About Workers page: "Unlike the New process command, a
worker process remains alive after the execution of the process method ends.”
Web process stay dormant for awhile and then die if no new
Does anyone know or can they find out the following?
What happens when workers die? 4D has at least two different approaches to
this:
* HTTP processes wait before dying, but then die if there are no new
requests after some time. (Or at least they used to.) Meaning, an HTTP
process may or may not
5 matches
Mail list logo
