First, setup a JETTY_BASE. Don't skip this. Don't modify the jetty distribution. This is important, don't avoid this. Future versions of Jetty will *only* support a proper JETTY_BASE vs JETTY_HOME split.
Next, don't use -Djava.io.tmpdir=/tmp on ubuntu, that's not going to work for services that last longer then 2 hours (as ubuntu cleans out the system /tmp directory periodically, breaking many java server libraries) Next, create a $JETTY_BASE/work directory, and do not specify -Djava.io.tmpdir. Let Jetty control its own work directory. Next, move the following command line options to your $JETTY_BASE/start.ini (or equivalent $JETTY_BASE/start.d/*.ini file) jetty.logging.dir=/opt/jetty/logs // <-- this should be your $JETTY_BASE/logs directory jetty.port=7070 Next, remove jetty-logging.xml from your command line (that's 100% inappropriate there). Joakim Erdfelt / [email protected] On Fri, Aug 19, 2016 at 8:48 AM, Michael McInness <[email protected]> wrote: > Apologies for being vague. What I see is thus: I start Jetty with "service > jetty start". I deploy a WAR (it's a simple CXF REST service), test it, > debug code, redeploy. Through all of this I'm tailing the *stderrout.log > and periodically see nothing logged when I redeploy the WAR. When this > happens I do "ps -ef | grep jetty" and find no JVM running. Would you > classify that as a crash or an exit? I'll call it a crexit until I know > more. I do "service jetty start" and it starts back up and the whole cycle > repeats. What do I expect? I'll take that as a rhetorical question from > someone who kindly helps others here but grows weary of noobs, as I > probably would, too. > > I'll enable DEBUG logs and will report back. Thanks for your help. > > > > On Fri, Aug 19, 2016 at 11:17 AM, Simone Bordet <[email protected]> > wrote: > >> Hi, >> >> On Fri, Aug 19, 2016 at 5:07 PM, Michael McInness <[email protected]> >> wrote: >> > I'm writing because the service stops periodically throughout the day >> as I >> > am testing (and frequently hot deploying) a WAR. >> >> You have to be more specific. The JVM process exits ? JVM crash ? >> What do you mean by "the service stop" ? What do you expect and what >> happens instead ? >> >> We have Jetty running in Ubuntu as a service like you have, running >> happily for months. >> >> If you enable Jetty DEBUG logs, what do you see before "the service >> stops" ? >> >> -- >> Simone Bordet >> ---- >> http://cometd.org >> http://webtide.com >> Developer advice, training, services and support >> from the Jetty & CometD experts. >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > > > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
