Re: [jetty-users] jetty for production : run as a service + log manageme

[Michele Rossi <michele.rossi@xxxxxxxxx>]

hi,

I haven't really had time to read the whole conversation but for what is worth, I also think that the jetty forking behaviour is problematic when running as a service.

I had to hack heavily the start.ini and re-create within it the entries that some .MOD modules would have brought in so that I could avoid forking.

Also I struggled a bit in finding an acceptable way to run Jetty as a service on Linux.

If you use a normal service you don't get auto-restart in case of crashes.

I settled for the use of the Upstart daemon ("initctl" commands) etc but I have to say that the Jetty docs weren't of much help to sort this out.

I found it surprising because if you run a web server chances are you want it executed right away if you bounce the machine and also restarted automatically if it crashes.

I think it would deserve its own chapter in the docs.

That said, I am aware it's all free and I am not complaining. 

Unfortunately I have zero time to contribute to these docs myself.

thanks,

Michele

On 15 September 2017 at 10:36, mh@xxxxxxx <mh@xxxxxxx> wrote:

Hi Joakim,

thanks for your help, I have read the rest of your message. Before
anything else I want to clear out something :

Le 14/09/2017 à 21:40, Joakim Erdfelt a écrit :
> This behavior, forking a new instance if --exec is used is common and
> desired.

I understand very well it is desired, even if I don't understand why it
is needed for options other than --exec like --module=logging-logback.
Than one makes the instance to fork too, even if --exec is not enabled.

My original point was about jetty.sh : It can't handle forking jetty
well. This is a fact, I have explained this in the mentionned github
issue :  I would suggest to use pgrep -P <mainprocesspid> so the script
can wait that the child processed died BEFORE the state file is removed.

I'll do a PR about it if get time to...
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users