Needed to verify if there is a client application trying to access the VSM using the incorrect transport protocol.
Won't be able to see the number of transactions increasing the Portal under Monitor, VSE. These transactions are failing before the VSM is processing them.
To help to troubleshoot it, use Wireshark in the VSE server and configure it to capture traffic while these messages are printed in the VSE log files.
By analyzing the captured traffic, can try to identify which addresses are trying to reach the VSE in which ports.
Can also see these messages when a vulnerability scan is running against the VSE server, however, when that is the case, will also see some other exceptions and it usually is for a specific period of time.