Where is this exception triggered in the BaseX paradigm? Is this just the usual stack trace from Java which normally has little value in determining a causation?
…close to impossible for me to say more about it, I’m sorry. You could launch your BaseX instance(s) with debugging enabled [1] and share the full stack traces with us, maybe that gives us more hints.
Best, Christian