On Tue, 2021-04-27 at 14:07 +0000, Bondeson, Carl wrote: > Where is this exception triggered in the BaseX paradigm?
The message comes from the Windows-native socket implementation. Some things to try - * a server on the same machine as the test client * a server on Linux instead of Windows * run the client on Linux instead of Windows any of these may still fail but with different error messages. If everything works on the local machine it might be a problem with a firewall, or a virus checker, especially if the problem goes away on Linux. It's also possible to trace network traffic to try & work out if the problem is in the client or in the server. Obvious thing to chek - make sure you're using the right classes in the client to communicate with BaseX. Which JVM version exactly are you using? Liam -- Liam Quin, https://www.delightfulcomputing.com/ Available for XML/Document/Information Architecture/XSLT/ XSL/XQuery/Web/Text Processing/A11Y training, work & consulting. Barefoot Web-slave, antique illustrations: http://www.fromoldbooks.org
