Re: MySQL java.net.SocketException: Broken pipe

[YoungSun Kim]

i also met this error today and got a solution..
i use unter envs below .
- JDK FullVersion : 1.4.2_04
- WebLogic Server Version : 8.1.2.0
- Service Pack Version :
- Platform & OS Version : SunOS 5.9
- Driver class name : org.gjt.mm.mysql.Driver

i met the error msg like this..

<2006. 5. 1. 오전 11시 37분 18초 KST> <Error> <JDBC> <BEA-001131> <Received an exception when closing a cached statement for the poo
l "mysqlmaster": com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:

** BEGIN NESTED EXCEPTION **

java.net.SocketException
MESSAGE: Broken pipe

STACKTRACE:

java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.ja va:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136 )
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream .java:66)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java: 124)
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2689)
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2618)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1551)
at com.mysql.jdbc.ServerPreparedStatement.realClose(ServerPrepar edStatement.java:877)
at com.mysql.jdbc.ServerPreparedStatement.close(ServerPreparedSt atement.java:453)
at weblogic.jdbc.common.internal.ConnectionEnv.getCachedStatemen t(ConnectionEnv.java:865)
at weblogic.jdbc.common.internal.ConnectionEnv.getCachedStatemen t(ConnectionEnv.java:794)
at weblogic.jdbc.wrapper.Connection.prepareStatement(Connection. java:343)
at com.nate.sms.dao.FREEDAO.maniFreeCount(FREEDAO.java:660)

and i guessed whether this container returns the connection to be used into the connection pool and the connection can't be connected and be broken .. so, I setted up the connection options like this..

1. configuration -> Connections -> Advanced Options -> Test Reserved Connections, Test Released Connections checked..
2. at configuration -> Connections -> Advanced Options -> test table name, filled by a dummy table..

my purpose is to reconnect not to be disconnected..

and so, until now it is good..