Hi,
I just encountered two problems:
I'm using a collection created wit UPDINDEX TRUE using BaseX75-20121114. When I tested it, everything worked fine, the index was recreated each time I stored or deleted something. However, today one of the users really worked with the whole webapplication and after half an hour (searching two collections, storing some new nodes and updating some nodes), she got a server time out.
In the GUI I could see, that the value of INDEX for "up-to-date" was "false". Which obviously caused the time out. But what could be the reason the index wasn't up to date anymore? How can I make sure the option is working as intended?
Anyway, I decided to get the latest snapshot BaseX75-20121204 and re-create the collection with again setting UPDINDEX TRUE.
For the webapplication I have a Linux server:
Linux version 2.6.18-274.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-50)) #1 SMP Fri Jul 22 04:43:29 EDT 2011
with
java version "1.6.0_07" Java(TM) SE Runtime Environment (build 1.6.0_07-b06) Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
For development, I use a Mac with OSX 10.6.8.
with
java version "1.6.0_37" Java(TM) SE Runtime Environment (build 1.6.0_37-b06-434-10M3909) Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01-434, mixed mode)
So I installed the latest snapshot on both and then tried to stop and restart the server. Which worked as usually fine on the Mac, but on the Linux server, when calling
basexserver stop
nothing happens. It looks like the script is waiting for some input -- the process does not stop. The old BaseX server seems to be running somehow; I cannot start the server either.
Is this a known issue with the latest version? How can I force basexserver to stop and then restart it again?
Best regards
Cerstin
Hi Cerstin,
In the GUI I could see, that the value of INDEX for "up-to-date" was
"false".
this information simply indicates that not all index structures are updated yet. Whenever you activate UPDINDEX, your text and value will always be updated (i.e., "Text Index: " should always be followed by the flag "ON").
nothing happens. It looks like the script is waiting for some input -- the
process does not stop. The old BaseX server seems to be running somehow; I cannot start the server either.
maybe there's still a process running server-side? What output do you get when calling the SHOW SESSIONS command?
Best, Christian
Hi Christian,
Am 04.12.2012 um 18:09 schrieb Christian Grün:
In the GUI I could see, that the value of INDEX for "up-to-date" was "false".
this information simply indicates that not all index structures are updated yet. Whenever you activate UPDINDEX, your text and value will always be updated (i.e., "Text Index: " should always be followed by the flag "ON").
OK, I will have a look at this as soon as I can start my application again.
nothing happens. It looks like the script is waiting for some input -- the process does not stop. The old BaseX server seems to be running somehow; I cannot start the server either.
maybe there's still a process running server-side? What output do you get when calling the SHOW SESSIONS command?
It says 0 sessions. However, calling "basexserver" from the command line gives:
Server ist running or permission was denied
It has nothing to do with user rights, the "permission" part does not apply.
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".
Any ideas?
-- 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.chmailto:cerstin.mahlow@unibas.ch Web: http://www.oldphras.nethttp://www.oldphras.net/
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. By the way, even if the process is killed, the server will try to flush and close open databases.
Hope this helps, Christian
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.chmailto:cerstin.mahlow@unibas.ch Web: http://www.oldphras.nethttp://www.oldphras.net/
Hi Cerstin,
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.
feel free to give us an update if this should again.
However, I know that she is still using IE for Web things. Could IE cause some problems when sending and receiving forms calling BaseX?
I doubt that this problem is related to client-specific settings. In all cases, we’d probably need to try to reproduce the behavior in order to say more.
Christian
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
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
basex-talk@mailman.uni-konstanz.de
-
Cerstin Elisabeth Mahlow -
Christian Grün -
Mahlow Cerstin