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