stoping xQuery transformation in eXist datasource takes very long
Posted: Thu Feb 02, 2017 3:01 pm
I have configured oXygen to connect to my development eXist-db (v2.2) via preferences -> add datasource etc. I use oXygen as editor to run xQuery scripts stored in my db (via associate transformation scenario), all is running great. However, I notice that when I wish to interrupt a running transformation by clicking on the red square "stop transformation" in the editor. The command does not seem to get executed on the server.
If i abort the transformation via eXist-db's monex app, the process is killed within a few seconds, I have yet to wait long enough for the stop instruction send from oXygen to actually take effect (10min+).
It seems that oXygen's connection to exist doesn't quite execute aborts the same way eXist does. It would be a great deal more convenient if abort could be more reliably triggered from inside oXygen.
To test take any Xquery that requires a few minutes of execution, and press abort after a few seconds of it running. wait…
Start the same query again from within oXygen and click stop execution in the Running Queries section of eXist-db monex app.
If i abort the transformation via eXist-db's monex app, the process is killed within a few seconds, I have yet to wait long enough for the stop instruction send from oXygen to actually take effect (10min+).
It seems that oXygen's connection to exist doesn't quite execute aborts the same way eXist does. It would be a great deal more convenient if abort could be more reliably triggered from inside oXygen.
To test take any Xquery that requires a few minutes of execution, and press abort after a few seconds of it running. wait…
Start the same query again from within oXygen and click stop execution in the Running Queries section of eXist-db monex app.