Status/Resolution/Reason: To Track//PRNeedInfo
Reporter/Name(from Bugbase): Paul Turner / ()
Created: 11/08/2018
Components: Web Socket, WebSocket Proxy
Versions: 2018
Failure Type: Usability Issue
Found In Build/Fixed In Build: 2018.0.01.311402 and below /
Priority/Frequency: Normal / Some users will encounter
Locale/System: / Win 2016
Vote Count: 1
Problem Description:
Intermittently, cfwebsocket connections via WebSocket Proxy will fail to subscribe to an established channel. With the WSProxy instance setup with logging enabled, we have been able to find that page hits where the Websocket connection fails to be established with return an entry "CF WSProxy Log WebSocket handler is not available"
Additionally, I would note that we have attempted increasing and decreasing the number of ports used by the WSPoxy instance, as well as setting up a dedicated IIS Application pool for the "CFWS" application under the site(s) to run on. However, the behavior has not changes despite these changes.
Furthermore, we have been able to find that this issue is not present when utilizing the "Built-in WebSocket Server" option, however our need for utilizing secure websockets on multiple domains that utilize their own SSL certificates is prevents us from utilizing the Built-in option since the Keystore only supports a single certificate.
**ColdFusion Admin Settings Screenshot : CF2018 - WebSocket Proxy Intermittent Unavailability - CFAdmin WebSocket Settings.png
**WSProxy settings Screenshot : CF2018 - WebSocket Proxy Intermittent Unavailability - WSProxy Connector Settings.png
Steps to Reproduce:
To reproduce this issue we are simply implementing the attached files in a site and hitting the index.cfm page.
Actual Result:
The index.cfm page will fail to produce the output of the Websocket subscription \ connection at the top of the page. Additionally messages posted via the page will fail to be sent. When this occurs the WSProxy instance will log an entry for ""CF WSProxy Log WebSocket handler is not available""
**Example Output of test page and log depicting intermittent behavior included in file (CF2018 - WebSocket Proxy Intermittent Unavailability - Example with Log output.gif)
Expected Result:
The index.cfm page should produce the output of the Websocket subscription \ connection at the top of the page. Furthermore, once loaded in multiple tabs \ windows data should be able to be posted in one form and then displayed on all open instances.
**Example Output of test page and log depicting intermittent behavior included in file (CF2018 - WebSocket Proxy Intermittent Unavailability - Example with Log output.gif)
Any Workarounds:Attachments:
Comments: