Are there any known issues with multiple simultaneous connections or

query executions

None that at least I am aware of. Have you encountered problems, or have you rather been distracted by the (unexpected) error message output?

Matthew Dziuban mrdziuban@gmail.com schrieb am Di., 17. Aug. 2021, 23:34:

Hi Christian,

Apologies for the delay on my end. Unfortunately I can't reproduce it consistently, but it seems to happen most often when I run another query (either via the REST interface of the java client) while the original query is still running. Are there any known issues with multiple simultaneous connections or query executions?

Thanks, Matt

On Thu, Aug 12, 2021 at 1:59 PM Christian Grün christian.gruen@gmail.com wrote:

...

Hi Matt,

It’s difficult to give a general answer. Do you think you can share a reproducible test case with us?

Thanks in advance Christian

On Thu, Aug 12, 2021 at 3:01 PM Matthew Dziuban mrdziuban@gmail.com wrote:

...

Hi all,

I'm using the java ClientSession class defined in the basex-api module

and I'm seeing intermittent org.basex.core.BaseXException errors with an empty error message when executing long-running read queries or CREATE DB commands. The stack trace of the most recent error points to ClientSession.receive ( https://github.com/BaseXdb/basex/blob/9.5.2/basex-core/src/main/java/org/bas... )

...

org.basex.core.BaseXException: org.basex.api.client.ClientSession.receive(ClientSession.java:190) org.basex.api.client.ClientSession.send(ClientSession.java:178) org.basex.api.client.ClientSession.send(ClientSession.java:215) org.basex.api.client.ClientSession.create(ClientSession.java:128) ...

Unfortunately since the message is empty it's difficult to debug what's

going wrong. I've checked the log files in basex/data/.logs but haven't found any information about the failure. Is there another place I can look? Or do you have any other recommendations for debugging the errors?

...

Thanks in advance, Matt