From 8835ff0d892c15c08d2b994cc00e04201fdd6ee7 Mon Sep 17 00:00:00 2001 From: Michael Meeks Date: Sat, 26 Oct 2024 15:37:05 +0100 Subject: [PATCH] Don't shutdown UDS websockets. We have one to the Kit process - that is allowed to take way longer than the ping time to respond, and it was not clear that this new close behavior on ping/ping was introduced in: e8a3cebcb9fd61dea61785a117df289c4029e029 Which also appears to add a 2 second non-responding websocket ping timeout for some reason (!?). Signed-off-by: Michael Meeks Change-Id: Iad74f253bdac5636757b130b299b5deacda658db --- net/WebSocketHandler.hpp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/net/WebSocketHandler.hpp b/net/WebSocketHandler.hpp index 48986ea67a68b..535e4b4719674 100644 --- a/net/WebSocketHandler.hpp +++ b/net/WebSocketHandler.hpp @@ -674,7 +674,8 @@ class WebSocketHandler : public ProtocolHandlerInterface LOG_WRN("CheckTimeout: Timeout websocket: Ping: last " << _pingMicroS.last() << "us, avg " << _pingMicroS.average() << "us >= " << _pingTimeout.count() << "us over " << (int)_pingMicroS.duration() << "s"); - shutdownSilent(); + if( isIPType() ) + shutdownSilent(); return true; } if (!_pingMicroS.initialized() || (_pingPeriod > std::chrono::microseconds::zero() &&