Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
2.4.16
-
None
-
MXS-SPRINT-127, MXS-SPRINT-128, MXS-SPRINT-129
Description
User reported the following error during maxscale switchover.
Thread: TaskThread@5e135ee8 Thread[http-nio-xxx.xxx.xxx.xxx-8080-exec-19,5,main] RUNNABLE |
java.net.SocketInputStream.socketRead0(Native Method)
|
java.net.SocketInputStream.socketRead(SocketInputStream.java:116) |
java.net.SocketInputStream.read(SocketInputStream.java:171) |
java.net.SocketInputStream.read(SocketInputStream.java:141) |
java.io.FilterInputStream.read(FilterInputStream.java:133) |
org.mariadb.jdbc.internal.io.input.ReadAheadBufferedStream.fillBuffer(ReadAheadBufferedStream.java:131) |
org.mariadb.jdbc.internal.io.input.ReadAheadBufferedStream.read(ReadAheadBufferedStream.java:104) |
org.mariadb.jdbc.internal.io.input.StandardPacketInputStream.getPacketArray(StandardPacketInputStream.java:247) |
org.mariadb.jdbc.internal.io.input.StandardPacketInputStream.getPacket(StandardPacketInputStream.java:218) |
org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.readPacket(AbstractQueryProtocol.java:1532) |
org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.getResult(AbstractQueryProtocol.java:1513) |
org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.readRequestSessionVariables(AbstractConnectProtocol.java:986) |
org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.readPipelineAdditionalData(AbstractConnectProtocol.java:1032) |
org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.postConnectionQueries(AbstractConnectProtocol.java:873) |
org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.createConnection(AbstractConnectProtocol.java:588) |
org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.connect(AbstractConnectProtocol.java:489) |
org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.handleIoException(AbstractQueryProtocol.java:2046) |
org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.readPacket(AbstractQueryProtocol.java:1534) |
org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.getResult(AbstractQueryProtocol.java:1513) |
org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.readPipelineAdditionalData(AbstractConnectProtocol.java:1024) |
org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.postConnectionQueries(AbstractConnectProtocol.java:873) |
org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.createConnection(AbstractConnectProtocol.java:588) |
org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.connect(AbstractConnectProtocol.java:489) |
org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.handleIoException(AbstractQueryProtocol.java:2046) |
org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.readPacket(AbstractQueryProtocol.java:1534) |
org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.getResult(AbstractQueryProtocol.java:1513) |
org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.readPipelineAdditionalData(AbstractConnectProtocol.java:1024) |
org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.postConnectionQueries(AbstractConnectProtocol.java:873) |
org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.createConnection(AbstractConnectProtocol.java:588) |
org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.connect(AbstractConnectProtocol.java:489) |
org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.handleIoException(AbstractQueryProtocol.java:2046) |
org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.readPacket(AbstractQueryProtocol.java:1534) |
org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.getResult(AbstractQueryProtocol.java:1513) |
org.mariadb.jdbc.inter
|
connector team confirmed and suggested the below and also suggested to file a bug for this to maxscale team as connector team thinks this was fixed in earlier in maxscale, but it shows again.
For the error 'Thread: TaskThread@5e135ee8 Thread[http-nio-xx.xxx.x.xxx-8080-exec-19,5,main] RUNNABLE', engineering noted: |
=====================================================================================
|
There has a been a socket error during a query, then connector has create a new connection, get a new socket, but failed on queries post connection. |
There is 2 queries executed after successfull authentication, and according to error, those are pipelined ("set autocommit=1, ..." and a select), meaning the 2 commands are send to server, then connectors read the 2 answers. it would seems server send the result for first query, but never send the result of the select, so connector hangs waiting for select result. |
=====================================================================================
|
It seems that it is obvious why this thread was hung for that long. To overcome this situation, you could set the following option. Please try this option and let us know how it works for you. |
=======================================
|
usePipelineAuth = false |
=======================================
|