Bug #73497 Communication failer on start server with eclipse
Submitted: 7 Aug 2014 10:19 Modified: 7 Sep 2014 19:49
Reporter: Andreas Kellner Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.1.31 OS:Windows
Assigned to: CPU Architecture:Any

[7 Aug 2014 10:19] Andreas Kellner
The following failure error message comes when I try to start a mysql jdbc database server: 

com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.

For your support I would be very grateful 

Andreas Kellner

How to repeat:
This is a simple Code: 
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.sql.Connection;
import java.sql.DatabaseMetaData;
import java.sql.DriverManager;
import java.util.Properties;

public class DBMetaData {

	public static void main(String[] args){
		try {
			FileInputStream in = new FileInputStream("dbconnect.properties");
			Properties prop = new Properties();
		String driver = prop.getProperty("driver"); 
		String url = prop.getProperty("url"); 
		String user = prop.getProperty("user"); 
		String password = prop.getProperty("password");
		if(driver != null)
		Connection con = DriverManager.getConnection(url,user,password); 
		DatabaseMetaData dbmd = con.getMetaData(); 
		System.out.println("URL " + dbmd.getURL());
		System.out.println("UserName" + dbmd.getUserName());
		System.out.println("DataBaseProductName  " + dbmd.getDatabaseProductName());

		} catch (FileNotFoundException e) {
			// TODO Auto-generated catch block
		catch(Exception ex){
[7 Aug 2014 19:49] Sveta Smirnova
Thank you for the report.

Are you trying to connect from Java application to MySQL Server 5.1.31? Which version of Connector/J do you use?
[8 Sep 2014 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".