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

Robert Stewart wrote:
> If you search the forums you can find a lot of other posts on this issue. The change is that the server kills connections that are idle for longer than wait_timeout. When your client app tries to use a connection that has been killed, the error below occurs when the client tries to read from the socket.
>   
Yeah, I've probably read all of those threads :) I don't think this is
the complete answer though. I get this error when trying to connect, not
when I'm using the connection. My guess is that the server kills the
connection but somehow allocates some other part of the system for a bit
longer making it impossible to create new connections.
> The new behavior is actually triggered by a change to the driver. I believe that the new behavior appeared in connector 3.0.8.
>   
That makes sense, we've upgraded from 3.0.5 to 5.0.6.

  

-- 
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]