Websocket connection fails with the error "Outbound handler not available yet"

Document ID : KB000005114
Last Modified Date : 14/02/2018
Show Technical Document Details

When utilizing a Gateway Websocket connection no response is received. The below errors will seen in the ssg logs.


WARNING 406 com.l7tech.external.assertions.websocket.server.WebSocketConnectionManager: No outbound handler exists for id 5282e59c9fcd45fe97ccfae2a62cdc55

WARNING 406 com.l7tech.external.assertions.websocket.server.WebSocketHandlerBase: Outbound handler not available yet

WARNING 406 com.l7tech.external.assertions.websocket.server.SSGInboundWebSocket: Failed to create connection to the server for websocket id=5282e59c9fcd45fe97ccfae2a62cdc55:1:HTTP/1.1. Reason:com.l7tech.external.assertions.websocket.server.WebSocketConnectionManagerException: Outbound handler not available yet

INFO    406 com.l7tech.external.assertions.websocket.server.SSGInboundWebSocket: Terminating SSGInboundWebSocket for URL: websocket id=5282e59c9fcd45fe97ccfae2a62cdc55:1:HTTP/1.1. Closing SSGInboundWebSocket. 




This is caused due to an undefined outbound URL as seen below:




To resolve the issue you must specify an outbound URL to a Websocket server.

For example, ws://echo.websocket.org:80


Note: If no port is explicitly set :80 will be automatically appended upon saving the connection.