This is a quick FYI for those running VMware View Connection Servers(Brokers/Managers). Regardless of whether you are using ‘Direct’ or ‘Tunnelled’ connections you may see these messages in your logs similar to the ones below with sequential request numbers.
(Request112) Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.io.IOException: Broken pipe
(Request111) Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.io.IOException: Broken pipe
The error messages are generally caused by an ADC or Load Balancer that is polling the Connection Servers web server, and forcing a close of the client connection. This is not something that the View Connection server is expecting to handle, so it dumps this message to the logs.
Essentially, its a false-positive in most cases, and I have heard on good authority that the VMware developers will change the log messages to something a little more friendly in future (~View 4.0).
If you’re seeing loads of these errors and your not using a Load Balancer, then you could have some clients out there that are pushing load generator scripts at your brokers, or potentially some idiot trying out his new script kiddie util. Check out vAudit from Richard Garsthagens site here – http://www.run-virtual.com/?dl_id=1 if you want more detail around successful and unsuccessful user logins. Its a great utility for those running View 3.x environments.