If a client connects to the message broker, and disconnects without going through a complete messaging session, an EOFException is logged at WARN level. This is disconcerting for administrators, because there is often no problem that needs to be investigated. It's particularly troublesome because installations that have this problem, tend to have it a lot.

This problem has been reported in various forms many times (ENTMQ-2010, for example).
However, I'm not sure the full extent of the problem in the field has been appreciated.

A case can be made that if a messaging client starts a session and does not complete it, that needs to be reported. However, ActiveMQ reports a problem if the client does no more than issue a socket connect. Load balancers and proprietary monitoring frameworks probe the broker constantly, just to see if the service port is open. With ActiveMQ, there is no way even to tell whether the broker service is port is open, without getting a warning message. I've not come across any other middleware product behaving this way.

I think customers feel that the time has come to relegate this WARN message to a DEBUG, or at least to make it configurable.