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

Andreas Andersson <[email protected]> Fri, 25 May 2007 23:57:53 +0200
Newsgroups gmane.comp.db.mysql.java
Message-ID <[email protected]>
Christopher G. Stach II wrote:
> Andreas Andersson wrote:
>   
>> Hi!
>>
>> I'm running mysql 5.0.37 with mysql-connector-java-5.0.6. We just moved
>> from mysql 4.0.something and now we notice this annoying error.
>>
>> (full stacktrace)
>>
>> com.mysql.jdbc.CommunicationsException: Communications link failure due
>> to underlying exception:
>>
>> ** BEGIN NESTED EXCEPTION **
>>
>> 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:1956)
>>         at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2368)
>>         at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2867)
>>         at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:870)
>>         at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:3333)
>>         at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1232)
>>         at com.mysql.jdbc.Connection.createNewIO(Connection.java:2749)
>>         at com.mysql.jdbc.Connection.<init>(Connection.java:1553)
>>         at
>> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:285)
>>         at java.sql.DriverManager.getConnection(DriverManager.java:512)
>>         at java.sql.DriverManager.getConnection(DriverManager.java:171)
>>  
>> This all happens on new connections created after between 50 and 90
>> minutes uptime on my tomcat server. Several connections are in use (and
>> being reused until they are dropped by the server) during that time.
>>
>> I get nothing in the error log at all.
>>
>> I'll be thankful for any input on this. Thanks.
>>     
>
> Connection timeout and close on the server side?  Check wait_timeout?
>
>   
wait_timeout is 600, the same as it was on our old mysql 4 (with the old
connector 3.0.5). Could this have changed in some way?
Could I in some way have more verbose logging from mysql and log what's
happening at the serverside when I get these messages on the client side?

thanks

-- 
Andreas Andersson
Senior Developer

Travelstart <http://www.travelstart.se>

Travelstart Nordic AB
Davidshallsgatan 14
211 45 Malmö

www.travelstart.se <http://www.travelstart.se>
www.travelstart.dk <http://www.travelstart.dk>
	  	Tel +46 (0)40-690 38 83
Mob +46 (0)70-757 23 73
Fax +46 (0)40-611 17 78

www.travelstart.no <http://www.travelstart.no>
www.travelstart.co.za <http://www.travelstart.co.za>


-- 
MySQL Java Mailing List
For list archives: http://lists.mysql.com/java
To unsubscribe:    http://lists.mysql.com/[email protected]