Mysql [Warning] Aborted connection

2015-08-01 11:13:31 5736 [Warning] Aborted connection 668 to db: 'dbname' user: 'dbuser' host: '' (Got an error reading communication packets)

We have java 10 servers connecting to DB, at times we are seeing error like this, please let me know what should be done to solve the types of errors?

We are using Mysql percona
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sivaatluriAuthor Commented:
My.cnf configuration


port                           = 3306
socket                         = /var/lib/mysql/mysql.sock

user                           = mysql
default-storage-engine         = InnoDB
socket                         = /var/lib/mysql/mysql.sock
pid-file                       = /var/lib/mysql/
# MyISAM #
key-buffer-size                = 32M
myisam-recover                 = FORCE,BACKUP
max-allowed-packet             = 16M
max-connect-errors             = 1000000
datadir                        = /srv/mysql/

server-id                      = 1
log-bin                        = /srv/mysqllogs/mysql-bin
max_binlog_size                = 512M
expire-logs-days               = 4
sync-binlog                    = 1

tmp-table-size                 = 128M
max-heap-table-size            = 128M
query-cache-type               = 1
query-cache-size               = 512M
max-connections                = 4096
thread-cache-size              = 100
open-files-limit               = 65535
table-definition-cache         = 4096
table-open-cache               = 10240

innodb-flush-method            = O_DIRECT
innodb-log-files-in-group      = 2
innodb-log-file-size           = 256M
innodb-flush-log-at-trx-commit = 1
innodb-file-per-table          = 1
innodb-buffer-pool-size        = 5G

log-error                      = /srv/mysqllogs/mysql-error.log
general_log_file        = /srv/mysqllogs/mysql.log
general_log             = 1
log_warnings = 2

log-queries-not-using-indexes  = 1
Since java 10 is prerelease problems should be expected and it must be operated by professionals who know how to fix bugs.

what are ulimits (ulimit -a) passed to MySQL daemon?
sivaatluriAuthor Commented:

 Its not Java 10, its JDK 6.. Not sure how Mysql Problems are related to java.

How I check the ulimit values set for mysql
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

warning is not a problem
usually Linux allows 1024 file descriptors per user unless you edit limits.conf
table_open_cache + max_connections or open file limit hardly fits in there
the parameters are so off real world that I can only suggest running and make recommended adjustments.
Bhavesh ShahLead AnalysistCommented:

did you checked the below link?

you might get an idea

can you share the log file.?
NerdsOfTechTechnology ScientistCommented:
Make sure all your users are calling mysql_close() on exit.

Users could be timing out without requests (sleeping time out).

It might even be chalked up to a really bad and/or slow network connection.

Check your logs for more details

More more common issues related to this error, also see:
sivaatluriAuthor Commented:
I have separate mysql-error log

Its logs only lines like this

2015-08-01 11:13:31 5736 [Warning] Aborted connection 668 to db: 'dbname' user: 'dbuser' host: '' (Got an error reading communication packets)

Network connection issues are not applicable as we are on Ec2 cloud. Networking is perfect

Any thing else you can help me with?
There is no error.
Figure out why client did running on not close mysql connection correctly or mask out this warning message.
NerdsOfTechTechnology ScientistCommented:
They are likely timing out or not closing the connection, and the server is closing the connection for them.

It might help to have more than one user name to pinpoint the user who is throwing the warning too.
sivaatluriAuthor Commented:
Does that mean the client running on haven't received response in the required time & closed the connection.


The Mysql is not accepting new connections because it's connections are full & keep putting the client in queue due to which the client has closed the connection.
Most likely client crashed without closing the socket.
NerdsOfTechTechnology ScientistCommented:
As the author hypothesized, the open connections and time outs may be filling up slots faster than the server can recycle them for additional users to logon.
gheistCommented: should tell on the spot what is wrong.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
MySQL Server

From novice to tech pro — start learning today.