[CONJ-320] handling socketTimeout with solution to avoid synchronisat…

…ion between write and read

src/main/java/org/mariadb/jdbc/internal/protocol/AbstractConnectProtocol.java

@@ -1023,4 +1023,9 @@ public ReadPacketFetcher getPacketFetcher() {
     public void changeSocketTcpNoDelay(boolean setTcpNoDelay) throws SocketException {
         socket.setTcpNoDelay(setTcpNoDelay);
     }
+
+    public void changeSocketSoTimeout(int setSoTimeout) throws SocketException {
+        socket.setSoTimeout(setSoTimeout);
+    }
+
 }

src/main/java/org/mariadb/jdbc/internal/protocol/AsyncMultiRead.java

@@ -64,6 +64,11 @@ public AsyncMultiRead(ComStmtPrepare comStmtPrepare, int nbResult, int sendCmdCo
 
     @Override
     public AsyncMultiReadResult call() throws Exception {
+        // avoid synchronisation of calls for write and read
+        // since technically, getResult can be called before the write is send.
+        // Other solution would have been to synchronised write and read, but would have been less performant,
+        // just to have this timeout according to set value
+        if (protocol.getOptions().socketTimeout != 0)  protocol.changeSocketSoTimeout(0);
 
         if (readPrepareStmtResult) {
             try {
@@ -85,6 +90,7 @@ public AsyncMultiReadResult call() throws Exception {
                 }
             }
         }
+        if (protocol.getOptions().socketTimeout != 0)  protocol.changeSocketSoTimeout(protocol.getOptions().socketTimeout);
 
         return asyncMultiReadResult;
     }

src/main/java/org/mariadb/jdbc/internal/protocol/Protocol.java

@@ -263,4 +263,5 @@ void prologProxy(ServerPrepareResult serverPrepareResult, ExecutionResult execut
 
     void changeSocketTcpNoDelay(boolean setTcpNoDelay) throws SocketException;
 
+    void changeSocketSoTimeout(int setSoTimeout) throws SocketException;
 }