Bug #36395 java.sql.SQLException: Communication link failure: java.io.EOFException, underly

• Submitted: 29 Apr 2008 11:27
• Modified: 29 Apr 2008 11:38
• Reporter: dimitar nenchev
• Status: Not a Bug
• Category: MySQL Server
• Severity: S1 (Critical)
• OS: Linux
• CPU Architecture: Any

[29 Apr 2008 11:27] dimitar nenchev

Description:
Hi 

[ERROR] jdbc:mysql://[ip address]:3306/[application root name] froot [application name] SQLException caught (opening db con)
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:1394)
	at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:1538)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1929)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1906)
	at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:2520)
	at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:817)
	at com.mysql.jdbc.Connection.createNewIO(Connection.java:1782)
	at com.mysql.jdbc.Connection.<init>(Connection.java:450)
	at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:411)
.................. org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:562)
	at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679)
	at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
	at java.lang.Thread.run(Thread.java:534)

** END NESTED EXCEPTION **

	at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:1713)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1929)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1906)
	at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:2520)
	at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:817)
	at com.mysql.jdbc.Connection.createNewIO(Connection.java:1782)
	at com.mysql.jdbc.Connection.<init>(Connection.java:450)
	at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:411)
	at java.sql.DriverManager.getConnection(DriverManager.java:512)
	...............
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:562)
	at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679)
	at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
	at java.lang.Thread.run(Thread.java:534)
2008-04-08 03:07:03 [INFO] Cant create statemnt -null connection to DB (openQueryRS)
2008-04-08 03:07:03 [INFO] Cant execute query or open result set as the statement is null

How to repeat:
We have very serious problem with one application.
it is working fine during the day, but in the night( i suppose when it is not very used) happens at particular time this exception at random queries.

and after that it is working and so on at periods this is happen, so at the end of the night the application crashes (i think because no more connections are avaiable). 

the application is using MySql 4.1.22-standard-log on linux and tomcat 4.1 at windows server 2000 also using mysql-connector-java-3.0.15-ga-bin.jar 
I think it is configuration problem on the db server because same application on local at windows is working fine with no problems, but not sure (local is not so used and there has no such logs with this problem).

I have been searching many forums and mail lists but have nothing to fix this problem, please help. 

Thank you,
Dimitar

Suggested fix:
i think it is specific configuration for some variables on db server

[29 Apr 2008 11:38] Tonci Grgin

We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.

Explanation: Hi Dimitar. You have provided us with no useful info nor any means of repeating the problem. I am also almost 100% sure that if you follow http://bugs.mysql.com/search.php?search_for=EOFException&status=All&severity=&limit=10&ord... you'll find solution for your problem. Please next time search BugsDB prior to posting report. It can save you much time.