Re: [jetty-dev] auto-respawning of jetty running as a linux service

[Greg Wilkins <gregw@xxxxxxxxxxx>]

Sorry,

no insight from the jetty devs.   There are soooo many different deployment environments that we are basically agnostic on the subject.       Auto restart does sound like a good feature to have, but if it is not in the standard service start mechanism provided by an OS, it is beyond our scope to provide one.

cheers

 

On 4 May 2016 at 19:15, Michele Rossi <michele.rossi@xxxxxxxxx> wrote:

forwarding to Jetty-dev too - hope the message is not off-topic as it involves deployment and OS-specific issues.

thanks,

Michele

---------- Forwarded message ----------
From: Michele Rossi <michele.rossi@xxxxxxxxx>
Date: 4 May 2016 at 11:13
Subject: Fwd: auto-respawning of jetty as a linux service
To: jetty-users@xxxxxxxxxxx

hi,

we are running Jetty (9.3.X) on CentOS  6.5 (Kernel  2.6.32-431.el6.x86_64) and it's installed as a service using chkconfig.

What's missing is that the process does not restart if it dies or it's killed which is a real problem.

If you google for "linux service respawn" or "centos service respawn" you land on about 10 different options, some using a special application called daemon, some are outdated because inittab is no longer supported, some that don't seem to work (".conf" files under /etc/init/).

While I normally love Linux as a server environment I am really puzzled by how the OS developers managed to make so hard a feature that it's so useful, especially on server environments.

Does anyone here have any tips on how to solve this seemingly complex problem, preferably without using custom applications?

many thanks,

Michele

_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-dev

--

Greg Wilkins <gregw@xxxxxxxxxxx> CTO http://webtide.com