m running tomcat 6.0.13 on a redhat 4.1.1 and I'm seeing this all too often in the catalina.out log:

java.sql.SQLException: Communication link failure: java.io.EOFException, underlying cause: null
** BEGIN NESTED EXCEPTION **
java.io.EOFException
STACKTRACE:
java.io.EOFException
at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1395 )
at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO. java:1539)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.ja va:1930)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:11 6
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java :1279)
at com.mysql.jdbc.Connection.execSQL(Connection.java: 2281)
at com.mysql.jdbc.PreparedStatement.executeQuery(Prep aredStatement.java:1634)
at com.uploadtracker.frontend.UPTRADRIVER.getSLAVESTA TUS(UPTRADRIVER.java:21
at com.uploadtracker.frontend.UPTRADRIVER.getTrack(UP TRADRIVER.java:202)
etc....

I've searched many forums/mail lists and cannot come up with a fix.
Any ideas as to what's causing this? Could it be a dodgy network or mishandling of connections? Would setting "autoReconnect" and/or "autoReconnectForPools" options to true in the connection strings help?
This doesn't actually cause any crashes, but its still a mystery to me.