stopping the basexhttp server
Saturday, 22 October 2011 · 7 messages · last reply 23 Oct 2011
CG
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
Quoted text · Pascal Heus · 21 lines
On Sat, Oct 22, 2011 at 9:37 PM, Pascal Heus <pascal.heus at 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 at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >
PH
Pascal Heus22 Oct 2011 23:37 #
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
CG
Quoted text · Pascal Heus · 3 lines
> Christian: > does this help in any way: > http://alaminsumon.blogspot.com/2009/06/how-to-stop-and-start-jetty-server-from.html
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
CG
Christian Grün22 Oct 2011 23:59 #
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
Quoted text · Christian Grün · 17 lines
On Sat, Oct 22, 2011 at 11:53 PM, Christian Grün <christian.gruen at gmail.com> wrote: >> Christian: >> does this help in any way: >> http://alaminsumon.blogspot.com/2009/06/how-to-stop-and-start-jetty-server-from.html > > 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 >
PH
Christian:
does this help in any way:
http://alaminsumon.blogspot.com/2009/06/how-to-stop-and-start-jetty-server-from.html *P
Quoted text · Christian Grün · 34 lines
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 at 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 at mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >>
PH
Here is another one:
http://ptrthomas.wordpress.com/2009/01/24/how-to-start-and-stop-jetty-revisited/ *P
Quoted text · Christian Grün · 34 lines
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 at 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 at mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >>
CG
Hi Pascal,
I gave it a try, and I added some code to stop the Jetty server [1,2]. Your feedback is welcome!
On Sunday, we planning the release of BaseX 7.0.1, mainly due to some updates in our distribution files. If everything goes well, the Jetty stop feature will already be part of it..
All the best,
Christian
[1] https://github.com/BaseXdb/basex-api/commit/a0394fa2587c080e7b9fa66ba1308bb6432a6873 [2] http://files.basex.org/releases/latest/
Quoted text · Pascal Heus · 21 lines
On Sat, Oct 22, 2011 at 9:37 PM, Pascal Heus <pascal.heus at 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 at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >
Written for BaseX 7.0. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery