| Re: [jetty-users] "jetty.sh stop" problem for 7.6.1 on Linux |
I did have --exec. Removing it solved the issue, but meant the arguments uncommented below it do not get used. The biggest concern is not being able to specify -Xmx to be able to use all the memory on the machine.
There is /etc/jetty.conf. I noticed the one line in it, "--pre=etc/jetty-logging.xml" did make it into the command line (what is that anyway?). Am going test just moving every commandline option from start.ini over to there.
Have not tested if the logging is fixed with the removal of --exec. Will require rebuild commenting out over rides. Will test after that of above.
----- Original Message -----
From: jesse.mcconnell@xxxxxxxxx
To: info@xxxxxxxxxxxxxxxxx
Sent: Thu, March 8, 2012, 11:12 AM
Subject: Re: [jetty-users] "jetty.sh stop" problem for 7.6.1 on Linux
are you using --exec?
we have seen some issues with it and have been thinking about just
removing the option altogether...its really only needed if you put jdk
cli options into the start.ini and there are other ways to handle
them...like the jetty.sh your using
so check your start.ini for --exec
it could be behind your other logging issues as well
jesse
--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx
On Thu, Mar 8, 2012 at 10:02, Jeff Palmer wrote:
> In my tests of 7.6.1, I found that stop only kills the daemon process, but
> not the actual server. It can be worked around, by then killing server your
> self, but it might cause file damage, etc depending on exactly what is
> happening at the time.
>
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
_______________________________________________ jetty-users mailing list jetty-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/jetty-users
-- thomas becker tbecker@xxxxxxxxxxx http://webtide.com / http://intalio.com (the folks behind jetty and cometd)