Aborted connection warnings on mysqld logs

Folks,

After some investigation we detected that the user for the MySQL Monitor on Maxscale is aborting lots of connections and making mysqld to log the below kinds of Warnings on the error log:

170710 10:28:24 [Warning] Aborted connection 4147497 to db: 'unconnected' user: 'unauthenticated' host: '10.0.127.40' (Got an error reading communication packets)

170710 10:28:34 [Warning] Aborted connection 4147522 to db: 'unconnected' user: 'unauthenticated' host: '10.0.127.40' (Got an error reading communication packets)

I cannot prove a theory I have around it, but, I think that if a thread delays too much to get authenticated, when for example a thread stays in `unauthenticated user` for more time then expected, it’s possibly considered by maxscale as inactivity and then, the connection/threads is not completed 100% as the thread is cut in the middle by the timeout signal - a not properly closed connection is one of the reasons to have that error.

As suggested, I got the following in place:

[root@maxscale ~]# maxadmin show monitor monitor
Monitor: 0x1bdb830
Name: monitor
Monitor running
Sampling interval: 100 milliseconds
MaxScale MonitorId: 0
Replication lag: enabled
Detect Stale Master: enabled
Connect Timeout: 1 seconds
Read Timeout: 1 seconds
Write Timeout: 1 seconds
Monitored servers: 192.168.50.11:3306, 192.168.50.12:3306, 192.168.50.13:3306

But I was not able to simulate that, is there something we can check further more? Why is it appearing only with the maxmon user?

Thanks!