I am creating a thread in init(), and starting it in start().
In the user guide, there is written:
"void stop(): Inform the Thread to terminate the run(), close the
ServerSockets".
So in stop() I am interrupting my thread.
In the apidocs, there is written "the container may restart the Daemon by
Hi Chris,
any new findings from your side?
Thanks in advance,
Siegfried Goeschl
> On 28 May 2017, at 21:41, Siegfried Goeschl
> wrote:
>
> Hi Chris,
>
> there are couple of things to consider
>
> * You are using a PumpStreamHander but the STDERR is not
These are just examples, depending on your use case. But I would agree that
thread is a bad one, as it is quite normal to create and start them in start.
Gruss
Bernd
--
http://bernd.eckenfels.net
From: Andrea Lo Pumo
Sent: Monday, June 5, 2017
Hi Siegfried,
I have implemented the executor watchdogs and shutdown hooks. I will know if
our efforts have been fruitful when we make our first restart which I'm sure
will be soon. I promise I'll write back and let you know how it goes.
Thank you vary much for checking in with me!
> On Jun
So I need to create the thread inside start() and not in init().
Why in the documentation it is suggested to create threads in init()?
"void init(String[] arguments): Here open configuration files, create a
trace file, create ServerSockets, Threads"
Thanks for the prompt reply.
2017-06-05 12:27
Hi Dan,
some thoughts along the line
* Just to make sure - you are running NOT on Windows?
* are you redirecting streams within your Java code and the Bash scripts? If
so, can you get rid of them? I vaguely remember issues where a process was
killed by the ExecuteWatchdog but hang on a