Confirmed, it is in the log file: 10:27:24.055 SERVER admin OK Server was started (port: 1984). 10:27:24.064 SERVER admin OK HTTP Server was started (port: 8080). 10:27:27.835 SERVER admin OK Server was stopped (port: 1984). 10:27:27.850 SERVER admin OK HTTP Server was stopped (port: 8080).
Any other ideas what could be done? Documentation here: https://docs.basex.org/wiki/Web_Application suggesting to switch Jetty verbose logging as follows: -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog -D{classref}.LEVEL=DEBUG But the basexhttp.bat file contains just SET and JAVA commands. Question: how to activate Jetty verbose logging? -----Original Message----- From: Christian Grün <christian.gr...@gmail.com> Sent: Tuesday, April 4, 2023 10:54 AM To: ykhab...@bellsouth.net Cc: BaseX <basex-talk@mailman.uni-konstanz.de>; Johan Mörén <johan.mo...@gmail.com> Subject: Re: [basex-talk] BaseX HTTP service goes down due to Qualys Agent > Is it possible that the Jetty stop call is not logged in the *.log files? I would be surprised (even more if there’s no request to the stop port). Just run basexhttp and basexhttp and check out the result: 16:49:45.431 SERVER admin OK HTTP Server was started (port: 80). 16:49:57.003 SERVER admin OK HTTP Server was stopped (port: 80). Does the problem persist with RESTXQ, WebSocket, and WebDAV removed? If you manage to create an environment in which you can also disable the BaseX REST service, and if Jetty goes down as well, it may be a problem that doesn’t relate to BaseX.
