Christian: does this help in any way: http://alaminsumon.blogspot.com/2009/06/how-to-stop-and-start-jetty-server-f... *P

On 10/22/11 4:48 PM, Christian Grün wrote:

Hi Pascal,

yes, this is a known issue, as we'd need to open yet another port for stopping Jetty (unfortunately, there is no other way to do this). I've added a GitHub issue:

https://github.com/BaseXdb/basex/issues/244

Hope this helps, Christian ___________________________

On Sat, Oct 22, 2011 at 9:37 PM, Pascal Heus pascal.heus@gmail.com wrote:

...

Hi: Under linux, I use the basexhttp script in the bin folder to start the BaseX server and Jetty HTTP server (for REST and Webdav)

To stop the process, I then copied the file into basexhttpstop nd added the stop keyword to the last line: java -cp "$CP" $VM org.basex.api.BaseXHTTP "$@" stop

However, this only seems to affect the BaseX server (Jetty continues to run and listen on port 8984). I can of course kill the process but would prefer for this to be available from the command line. Could this be adjusted?

thanks *P _______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

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