ReplicationConnection and wait_timeout
Posted by: Clive Cox
Date: June 26, 2006 01:04AM

I have problems if I set a "low" wait_timeout when using the ReplicationDriver.

I get the much discussed "communications link failure" on calls to setReadOnly when it attempts to swap to a slave connection.

Is this perhaps because the slave connection has been timed out at the server?

I am also using the DBCP connection pool. Are there any issues with using this with the ReplicationDriver?

Thanks,

Clive

-----




com.mysql.jdbc.CommunicationsException
MESSAGE: Communications link failure due to underlying exception:

** BEGIN NESTED EXCEPTION **

java.io.EOFException

STACKTRACE:

java.io.EOFException
at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1934)
at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2380)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2909)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1600)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1695)
at com.mysql.jdbc.Connection.execSQL(Connection.java:2998)
at com.mysql.jdbc.Connection.setCatalog(Connection.java:5028)
at com.mysql.jdbc.ReplicationConnection.swapConnections(ReplicationConnection.java:457)
at com.mysql.jdbc.ReplicationConnection.switchToSlavesConnection(ReplicationConnection.java:432)
at com.mysql.jdbc.ReplicationConnection.setReadOnly(ReplicationConnection.java:383)
at org.apache.commons.dbcp.DelegatingConnection.setReadOnly(DelegatingConnection.java:239)

Options: ReplyQuote


Subject
Written By
Posted
ReplicationConnection and wait_timeout
June 26, 2006 01:04AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.