broken pipe in parallel queries
Friday, 28 October 2016 · 3 messages · last reply 1 Nov 2016
GS
George Sofianos28 Oct 2016 15:35 #
I'm having some issues with running some queries in parallel. If I run the script on one file, I get the expected result (the execution time is about 40 seconds for this specific script). If I run the same script on many XML files, at the same time, I get a broken pipe error. I'm using a java BasexClient to execute the queries, and I'm trying to execute the script on about 50 files at the same time (the .basex parallel configuration is the default). Could this be related to basex? It could also be a network issue so I'm still investigating.
10/28/2016 4:10:21 PM Suppressed: java.net.SocketException: Broken pipe 10/28/2016 4:10:21 PM at java.net.SocketOutputStream.socketWrite0(Native Method)
10/28/2016 4:10:21 PM at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) 10/28/2016 4:10:21 PM at
java.net.SocketOutputStream.write(SocketOutputStream.java:159) 10/28/2016 4:10:21 PM at
org.basex.io.out.BufferOutput.flush(BufferOutput.java:60)
10/28/2016 4:10:21 PM at
org.basex.io.out.BufferOutput.write(BufferOutput.java:54)
10/28/2016 4:10:21 PM at
org.basex.io.out.PrintOutput.write(PrintOutput.java:66)
10/28/2016 4:10:21 PM at
org.basex.io.out.ServerOutput.write(ServerOutput.java:31)
10/28/2016 4:10:21 PM at java.io.OutputStream.write(OutputStream.java:116) 10/28/2016 4:10:21 PM at
org.basex.io.out.BufferOutput.flush(BufferOutput.java:60)
10/28/2016 4:10:21 PM at
org.basex.io.out.PrintOutput.flush(PrintOutput.java:141)
10/28/2016 4:10:21 PM at
org.basex.io.serial.OutputSerializer.close(OutputSerializer.java:82) 10/28/2016 4:10:21 PM at
org.basex.server.ServerQuery.execute(ServerQuery.java:143)
10/28/2016 4:10:21 PM ... 2 more
CG
Christian Grün28 Oct 2016 15:37 #
Quoted text · George Sofianos · 1 line
> It could also be a network issue so I'm still investigating.
I haven’t experienced exceptions of this kind so far, but if it turns out that BaseX is the black sheep, feel freeo to create an MVCE for us.
Quoted text · George Sofianos · 25 lines
> 10/28/2016 4:10:21 PM Suppressed: java.net.SocketException: Broken pipe > 10/28/2016 4:10:21 PM at java.net.SocketOutputStream.socketWrite0(Native > Method) > 10/28/2016 4:10:21 PM at > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) > 10/28/2016 4:10:21 PM at > java.net.SocketOutputStream.write(SocketOutputStream.java:159) > 10/28/2016 4:10:21 PM at > org.basex.io.out.BufferOutput.flush(BufferOutput.java:60) > 10/28/2016 4:10:21 PM at > org.basex.io.out.BufferOutput.write(BufferOutput.java:54) > 10/28/2016 4:10:21 PM at > org.basex.io.out.PrintOutput.write(PrintOutput.java:66) > 10/28/2016 4:10:21 PM at > org.basex.io.out.ServerOutput.write(ServerOutput.java:31) > 10/28/2016 4:10:21 PM at java.io.OutputStream.write(OutputStream.java:116) > 10/28/2016 4:10:21 PM at > org.basex.io.out.BufferOutput.flush(BufferOutput.java:60) > 10/28/2016 4:10:21 PM at > org.basex.io.out.PrintOutput.flush(PrintOutput.java:141) > 10/28/2016 4:10:21 PM at > org.basex.io.serial.OutputSerializer.close(OutputSerializer.java:82) > 10/28/2016 4:10:21 PM at > org.basex.server.ServerQuery.execute(ServerQuery.java:143) > 10/28/2016 4:10:21 PM ... 2 more
GS
George Sofianos1 Nov 2016 18:40 #
Quoted text · Christian Grün · 4 lines
>> It could also be a network issue so I'm still investigating. > I haven’t experienced exceptions of this kind so far, but if it turns > out that BaseX is the black sheep, feel freeo to create an MVCE for > us.
In case someone else has something similar, the problem was a timeout configuration of the load balancer. Thanks for pointing me to the right direction.
Written for BaseX 8.5. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery