Aborted connection to db (Got an error reading communication packets)

查看mysql日志发现有大量的这种错误

同时tomat日志里面有如下的日志：
2016-12-23 13:26:41,551 [Druid-ConnectionPool-Create-906657899] ERROR [com.alibaba.druid.pool.DruidDataSource] - create connection error, url: jdbc:mysql://*.*.*.*:3306/system?useUnicode=true&characterEncoding=utf-8&useSSL=true, errorCode 0, state 08S01

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.

at sun.reflect.GeneratedConstructorAccessor40.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.lang.reflect.Constructor.newInstance(Constructor.java:526)

at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)

at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:988)

at com.mysql.jdbc.MysqlIO.(MysqlIO.java:341)

at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2251)

at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2284)

at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2083)

at com.mysql.jdbc.ConnectionImpl.(ConnectionImpl.java:806)

at com.mysql.jdbc.JDBC4Connection.(JDBC4Connection.java:47)

at sun.reflect.GeneratedConstructorAccessor41.newInstance(Unknown Source)

at

****

Caused by: java.net.ConnectException: Connection refused

at java.net.PlainSocketImpl.socketConnect(Native Method)

查看mysql官方文档，有如下的解释：
B.5.2.11 Communication Errors and Aborted Connections

If connection problems occur such as communication errors or aborted connections, use these sources of information to diagnose problems:

• The error log. See Section 6.4.2, “The Error Log”.

• The general query log. See Section 6.4.3, “The General Query Log”.

• The Aborted_xxx and Connection_errors_xxx status variables. See Section 6.1.7, “Server Status Variables”.

• The host cache, which is accessible using the host_cache Performance Schema table. See Section 9.12.5.2, “DNS Lookup Optimization and the Host Cache”, and Section 24.10.16.1, “The host_cache Table”.

If you start the server with the log_error_verbosity system variable set to 3, you might find messages like this in your error log:

[Note] Aborted connection 854 to db: 'employees' user: 'josh'

If a client is unable even to connect, the server increments the Aborted_connects status variable. Unsuccessful connection attempts can occur for the following reasons:

• A client attempts to access a database but has no privileges for it.

• A client uses an incorrect password.

• A connection packet does not contain the right information.

• It takes more than connect_timeout seconds to obtain a connect packet. See Section 6.1.5, “Server System Variables”.

If these kinds of things happen, it might indicate that someone is trying to break into your server! If the general query log is enabled, messages for these types of problems are logged to it.

If a client successfully connects but later disconnects improperly or is terminated, the server increments the Aborted_clients status variable, and logs anAborted connection message to the error log. The cause can be any of the following:

• The client program did not call mysql_close() before exiting.

• The client had been sleeping more than wait_timeout or interactive_timeout seconds without issuing any requests to the server. SeeSection 6.1.5, “Server System Variables”.

• The client program ended abruptly in the middle of a data transfer.

Other reasons for problems with aborted connections or aborted clients:

• The max_allowed_packet variable value is too small or queries require more memory than you have allocated for mysqld. See Section B.5.2.10, “Packet Too Large”.

• Use of Ethernet protocol with Linux, both half and full duplex. Some Linux Ethernet drivers have this bug. You should test for this bug by transferring a huge file using FTP between the client and server machines. If a transfer goes in burst-pause-burst-pause mode, you are experiencing a Linux duplex syndrome. Switch the duplex mode for both your network card and hub/switch to either full duplex or to half duplex and test the results to determine the best setting.

• A problem with the thread library that causes interrupts on reads.

• Badly configured TCP/IP.

• Faulty Ethernets, hubs, switches, cables, and so forth. This can be diagnosed properly only by replacing hardware.

按照说明：  我在线修改了max_allowed_packet 没有效果！
然后我将my.cnf中的
wait_timeout            = 100
interactive_timeout     = 100

注释掉，然后重启mysqld，这两个值就恢复成默认的设置了！问题就解决了。
 了
这样虽然解决问题了，但有很大的隐患！