There's been a bug causing this behaviour somewhere in summer last year
and I fixed it. But might as well be something else blocking the
termination of the jvm.
So if we need to dig deeper into this, let me know. I will search my
brain for what exactly my fix was.
On Thu Mar 8 17:12:53 2012, Jesse McConnell wrote:
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
[email protected]
On Thu, Mar 8, 2012 at 10:02, Jeff Palmer<[email protected]> 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
[email protected]
https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/jetty-users
--
thomas becker
[email protected]
http://webtide.com / http://intalio.com
(the folks behind jetty and cometd)
_______________________________________________
jetty-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/jetty-users
