Btw, I forgot to mention that Jetty can already be stopped if Maven is used for running the HTTP Server, and if the basex-api/pom.xml is modified to use 8985 as stop port (but I guess this doesn't really help you):
http://docs.basex.org/wiki/Startup#BaseX_HTTP_Server https://github.com/BaseXdb/basex-api/blob/master/pom.xml#L205
If we use another port for stopping Jetty, we'll have to add this port in our configuration files, installers etc. As an alternative, we could always use Jetty port + 1 for stopping the server, which might be the easiest solution.
Suggestions are welcome, Christian ___________________________
On Sat, Oct 22, 2011 at 11:53 PM, Christian Grün christian.gruen@gmail.com wrote:
Christian: does this help in any way: http://alaminsumon.blogspot.com/2009/06/how-to-stop-and-start-jetty-server-f...
Pascal,
thanks for the links; and, yes, I know about those solutions.. The second link you posted describes a straightforward approach to monitor Jetty - and the first link references a solution from one of the Jetty distributions that includes basically the same code as proposed by the second solution. I'd be happy if we found yet another solution that doesn't need to watch an additional port..
Christian