<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Re: Reconnect the websocket when broken - Status changed to: Closed - Archived in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/Reconnect-the-websocket-when-broken/idc-p/2119349#M16620</link>
    <description />
    <pubDate>Mon, 18 Sep 2023 17:53:34 GMT</pubDate>
    <dc:creator>Ideation</dc:creator>
    <dc:date>2023-09-18T17:53:34Z</dc:date>
    <item>
      <title>Reconnect the websocket when broken</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Reconnect-the-websocket-when-broken/idi-p/1739843</link>
      <description>&lt;P&gt;Could Qlik Sense please attempt to reconnect to the websocket when the connection is lost?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When users on laptops disconnect from their docking station and go to wifi (or vica versa), all websockets will be dropped.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But other applications try calling home to reconnect. Qlik Sense doesn't, and this leads to much frustration.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This also applies when connecting to some VPNs, flaky wifi signals, etc.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Aug 2020 11:17:41 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Reconnect-the-websocket-when-broken/idi-p/1739843</guid>
      <dc:creator>vegard_bakke</dc:creator>
      <dc:date>2020-08-31T11:17:41Z</dc:date>
    </item>
    <item>
      <title>Re: Reconnect the websocket when broken</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Reconnect-the-websocket-when-broken/idc-p/1745519#M3513</link>
      <description>&lt;P&gt;Many network boxes kill idle websockets.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Azure Gateway defaults to killing any idle websockets after 4 minutes.&lt;BR /&gt;Can be configured to a maximim of 30 minutes.&lt;BR /&gt;&lt;A href="https://azure.microsoft.com/en-us/blog/new-configurable-idle-timeout-for-azure-load-balancer/" target="_blank" rel="noopener"&gt;https://azure.microsoft.com/en-us/blog/new-configurable-idle-timeout-for-azure-load-balancer/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If Qlik Server closed the connection with '&lt;SPAN&gt;OnSessionTimedOut', keep the current behaviour.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;But if the connection is just dropped, please redial.&amp;nbsp; And when redialing, consider adding a console message: 'Webcosket connection lost. Reconnecting. (Happend 04:00 minutes since the previous lost connection.)' OR at least state the time when it happened.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;In a complex network architecture, with multiple clouds, IT centers etc, timing the connection drop is the only information that can help you find the source.&lt;BR /&gt;If it always cuts out after 4 minutes, you start looking at the Azure Gateway.&lt;BR /&gt;If it always cuts after 2 minutes, you look in IBM WebSeal.&lt;BR /&gt;If it varies, it is not a timeout setting, but a flaky network.&amp;nbsp; Happy hunting. (But at least you know it is not a timeout setting, so you can skip investigating those.)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Sep 2020 09:36:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Reconnect-the-websocket-when-broken/idc-p/1745519#M3513</guid>
      <dc:creator>vegard_bakke</dc:creator>
      <dc:date>2020-09-21T09:36:09Z</dc:date>
    </item>
    <item>
      <title>Re: Reconnect the websocket when broken</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Reconnect-the-websocket-when-broken/idc-p/1860735#M7848</link>
      <description>&lt;P&gt;Qlik Sense Enterprise SaaS has a 30 second TCP keep-alive enabled for the WebSocket connection.&lt;BR /&gt;This means that an ideal session will not be closed prematurely, with the assumption that the TCP keep-alive packages are honored by all network devices in the routed path.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Nov 2021 03:25:27 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Reconnect-the-websocket-when-broken/idc-p/1860735#M7848</guid>
      <dc:creator>ToniKautto</dc:creator>
      <dc:date>2021-11-18T03:25:27Z</dc:date>
    </item>
    <item>
      <title>Re: Reconnect the websocket when broken</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Reconnect-the-websocket-when-broken/idc-p/1860929#M7851</link>
      <description>&lt;P&gt;And if I take my laptop out of the docking station....?&lt;BR /&gt;&lt;BR /&gt;or connect to a VPN that reroutes the traffic...?&lt;/P&gt;</description>
      <pubDate>Thu, 18 Nov 2021 11:36:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Reconnect-the-websocket-when-broken/idc-p/1860929#M7851</guid>
      <dc:creator>vegard_bakke</dc:creator>
      <dc:date>2021-11-18T11:36:17Z</dc:date>
    </item>
    <item>
      <title>From now on, please track this idea from the Ideation por...</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Reconnect-the-websocket-when-broken/idc-p/2119348#M16619</link>
      <description>&lt;P&gt;From now on, please track this idea from the Ideation portal.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;A title="Link to new idea" href="https://ideation.qlik.com/app/#/case/283176" target="_blank" rel="noopener"&gt;Link to new idea&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Meghann&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;EM&gt;NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you &lt;STRONG&gt;only&lt;/STRONG&gt; see 1 tab with the login page, please try clicking this link first: &lt;STRONG&gt;&lt;A title="Authenticate me!" href="#" target="_blank" rel="noopener"&gt;Authenticate me!&lt;/A&gt;&lt;/STRONG&gt;&amp;nbsp;t&lt;/EM&gt;&lt;EM&gt;hen try the link above again. Ensure pop-up blocker is off.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Sep 2023 17:53:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Reconnect-the-websocket-when-broken/idc-p/2119348#M16619</guid>
      <dc:creator>Meghann_MacDonald</dc:creator>
      <dc:date>2023-09-18T17:53:32Z</dc:date>
    </item>
    <item>
      <title>Re: Reconnect the websocket when broken - Status changed to: Closed - Archived</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Reconnect-the-websocket-when-broken/idc-p/2119349#M16620</link>
      <description />
      <pubDate>Mon, 18 Sep 2023 17:53:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Reconnect-the-websocket-when-broken/idc-p/2119349#M16620</guid>
      <dc:creator>Ideation</dc:creator>
      <dc:date>2023-09-18T17:53:34Z</dc:date>
    </item>
  </channel>
</rss>

