As discussed in a parallel thread, I’ve determined that the problem is caused by trying to transform a massive doc in the database using an XSLT transform that either never completes or fails in a way that
is not reflected in the log.
I performed a full-scale test on my development server, meaning that this was the only process running on it. I could see through my server status dashboard that the process doing the XSLT was running and
it took a *long* time to finish (at least 24 hours—I stopped watching it closely but checking it now it has completed successfully).
So the issue is with my attempt to transform a 300MB document, not an issue with BaseX itself.
The solution is clearly to not try to transform a 300MB document, which I’m pursing now.
I’ve yet to find a way, short of connecting BaseX to an interactive debugger, to get visibility into what it’s doing on the server—for example, I orchestrate my processes by creating a sequence of jobs but
there doesn’t seem to be a way to see what job is running or get insight into what it’s actively doing.
I’m not sure it’s even possible to provide that kind of visibility but it does make knowing what’s happening a challenge. Of course I can use messages in my code to get some feedback in the log, and I do do
that, but for just monitoring a running server it would be nice to have more visibility.
Cheers,
E.
_____________________________________________
Eliot Kimber
Sr. Staff Content Engineer
O: 512 554 9368
servicenow
LinkedIn | X | YouTube | Instagram