Hi Christian,

Am 06.12.2012 um 18:00 schrieb Christian Grün:

When trying to call "basexserver stop", nothing happens, it seems to wait
for something or process something. When I call basexserver stop, "java"
appears for a moment in "top", but then it disappears and the command does
not stop. Very frustrating. Calling "basexserver -S", shows the same
behavior -- although you would expect the same message like the one for
"basexserver".

Difficult to guess what’s going on here. My assumption is that there
must be a process waiting for something, and as the "stop" command
tries to gracefully shut shown the server, it won’t do anything.

Using Linux, you could check the list of open files and grep the
result for any basex-related files (eg: lsof | grep -i basex). If
there no database files are touched, it should be a safe bet to simply
kill your server process. 

OK, the only basex process running was the server started 20 days ago. I killed this one and then started the server again.

I have no idea what might have caused the time out my user encountered in the first place. The queries she ran were simple ones with only 150 and less results -- the execution should have been fast.  However, I know that she is still using IE for Web things.  Could IE cause some problems when sending and receiving forms calling BaseX?

Best regards

Cerstin
--
Dr. phil. Cerstin Mahlow

Universität Basel
Deutsches Seminar
Nadelberg 4
4051 Basel
Schweiz

Tel:  +41 61 267 07 65
Fax: +41 61 267 34 40
Mail: cerstin.mahlow@unibas.ch
Web: http://www.oldphras.net