Only SOCKS5 supported

We get this in the error logs regularly, every few minutes.

The reason behind this is, that we have a load balancer (HAProxy), which periodically “pings” the file transfer port 7777, but appearently does not speak the SOCKS5 protocol.

The problem is that the log is full of this error, which makes log analysis hard.

Can you think of any reasonable way to either prevent this, or don’t log it, or don’t log the whole stacktrace, or log it to debug?

Maybe a better idea is to return a proper error code to the client as specified in RFC 1928 - SOCKS Protocol Version 5 instead of just closing the socket.

In this case we can remove the logging imo.

2015.12.12 01:59:27 org.jivesoftware.openfire.filetransfer.proxy.ProxyConnectionManager - Error processing file transfer proxy connection Only SOCKS5 supported
    at org.jivesoftware.openfire.filetransfer.proxy.ProxyConnectionManager.processConnection(
    at org.jivesoftware.openfire.filetransfer.proxy.ProxyConnectionManager.access$200(
    at org.jivesoftware.openfire.filetransfer.proxy.ProxyConnectionManager$1$
    at java.util.concurrent.Executors$
    at java.util.concurrent.ThreadPoolExecutor.runWorker(
    at java.util.concurrent.ThreadPoolExecutor$