[
https://issues.apache.org/jira/browse/KNOX-2004?focusedWorklogId=345469&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345469
]
ASF GitHub Bot logged work on KNOX-2004:
----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Nov/19 17:58
Start Date: 18/Nov/19 17:58
Worklog Time Spent: 10m
Work Description: risdenk commented on issue #200: KNOX-2004 - Adding
changes for handling Ping/Pong message from backend server on websocket
connection
URL: https://github.com/apache/knox/pull/200#issuecomment-555134400
Error looks related to this change.
```
[ERROR] Errors:
[ERROR] WebsocketServerInitiatedPingTest.testGatewayServerInitiatedPing:95
» Timeout T...
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 345469)
Time Spent: 20m (was: 10m)
> 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
> Priority: Major
> Attachments: xx_cdap_timeout1.pcap
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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.4#803005)
