Hi Jan,
we've tracked down a very nasty issue with the stop script last week. The deadlock in the basexhttpstop should be fixed in the latest release [1].
The connection failure in the start script is strange because during startup of the HTTP server nobody should be trying to connect to its port.
Maybe you could share your automation scripts?
Regards,
Marco.

[1] http://files.basex.org/releases/latest/

On 07/03/2017 18:03, kalibuk@centrum.cz wrote:

Hallo,

I'm trying to get strating and stopping of BaseX HTTP server automated.

Whats wrong with starting:

Once trying to run in command line "basexhttp.bat -S"

I get "Connection failed (port: 8984)."

But server is running (!?) and I can create socket to comunicate with.

Whats wrong with stopping:

Once trying to run in command line "basexhttpstop.bat"

I get it hanged and need to terminate job or on another attempt I get back "Connection failed (port: 8985)."

And I cannot communicate with server so it seems that it really got stopped.

It's tricky to automate that if I get errors on every attempt to start/stop it. Could you advice?

Third error what I ocasionally can get back after trying to run server is:

"Error occurred during initialization of VM

Could not reserve enough space for 1433600KB object heap"

Behaviour is same for 8.6.0 and 8.6.1. I have just updated Java RT to latest.

Regards,

Jan, Brno