[jira] [Created] (KNOX-2004) Websockets connections between UI frontend and Knox are timing out as idle connections even though backend server is sending PING messages to keep connections alive

["Rajat Goel (Jira)" <ji...@apache.org>]

Rajat Goel created KNOX-2004:
--------------------------------

             Summary: Websockets connections between UI frontend and Knox are  timing out as idle connections even though backend server is sending PING messages to keep connections alive
                 Key: KNOX-2004
                 URL: https://issues.apache.org/jira/browse/KNOX-2004
             Project: Apache Knox
          Issue Type: Bug
          Components: Server
    Affects Versions: 1.0.0
         Environment: HDP 3.1.0
            Reporter: Rajat Goel
            Assignee: Rajat Goel
         Attachments: xx_cdap_timeout1.pcap

Websocket connection between UI client and Knox server is idle and gets timed out after configured socket idle timeout period whereas without Knox i.e. direct websocket connection from UI to Service backend never times out.

On debugging further, found that Service backend is a Node js server and uses websocket control messages (Ping, Pong) to keep websocket connective alive. Knox gateway was responding to backend with Pong message. However, Knox was not Proxying Ping messages to frontend which was resulting idle timeout of this side of connection.

Confirmed the same from TCP packet raw dump using Wireshark.

Attaching TCP packet dump. For checking Knox server to Service Backend websocket connection, use filter '(ip.src == 192.168.133.69) && (ip.dst == 192.168.133.69) && (tcp.port==39212)'

 

For Frontend UI to Knox websocket connection, use filter:

(ip.dst == 192.168.108.57) || (ip.src == 192.168.108.57) && (tcp.port==49610)



--
This message was sent by Atlassian Jira
(v8.3.2#803003)