websocket connection check doesn't attempt to connect to specified port.

[Former user]

Notes: * CentOS Linux release 7.2.1511 (Core) * Monit version 5.25.1 (Built with ssl, with ipv6, with compression, with pam and with large files) * Monit config with directives (valid per monit -t) as follows:

check host thalamus-dev.target.com address "thalamus-dev.target.com" if failed port 8001 protocol websocket host "thalamus-dev.target.com" request "/bt_events" origin "thalamus-dev.target.com" version 13 for 3 cycles then alert

• used tcpdump to confirm no connection attempts to port 8001.
• /var/log/messages contains entries as follows: monit[1110]: 'thalamus-dev.target.com' failed protocol test [WEBSOCKET] at [thalamus-dev.target.com]:8001/bt_events [TCP/IP] -- WEBSOCKET: response header read error -- Resource temporarily unavailable
• wrote a test app that successfully connects to port 8001 via the websocket protocol.
• verified connection to port 8001 (via tcpdump) when running aforementioned test app.

[Tildeslash]

The "WEBSOCKET: response header read error -- Resource temporarily unavailable" is logged, when the connection was established, but the response to either "ping" or "close" command timed out.

Please can you check on server side if it logs some errors? Maybe your websocket server doesn't implement ping or close.