I'm trying to create an environment where I can have mutliple BaseX Servers, and I can run 2-3 complex queries on them at a time. However, I want to have the ability to stop a running XQuery script for any reason. I assumed that's what would happen if I KILL the session using a BaseX client. However when I try to KILL a session I have the following issues:
1) BaseX client freezes and I have to CTRL-C to stop it 2) The session I try to kill is removed from the list, but the process continues to run. I have to force kill -9 the basex server for it to stop.
Should I report this as a bug or is there another way to kill the running scripts? Thanks
Hi George,
I did some quick tests, but I didn’t manage to reproduce the problem. Do you think you could build a little self-contained example for us, e.g. in Java, that shows what goes in wrong?
Thanks in advance, Christian
PS: I’ll be offline from May 7-21, so it might take a while for me to give you an answer.
On Fri, May 6, 2016 at 1:47 PM, George Sofianos gsf.greece@gmail.com wrote:
I'm trying to create an environment where I can have mutliple BaseX Servers, and I can run 2-3 complex queries on them at a time. However, I want to have the ability to stop a running XQuery script for any reason. I assumed that's what would happen if I KILL the session using a BaseX client. However when I try to KILL a session I have the following issues:
- BaseX client freezes and I have to CTRL-C to stop it
- The session I try to kill is removed from the list, but the process
continues to run. I have to force kill -9 the basex server for it to stop.
Should I report this as a bug or is there another way to kill the running scripts? Thanks
basex-talk@mailman.uni-konstanz.de