Qlik Community

Qlik Sense Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

Announcements
Uploads getting stuck in the virus scanner. We are investigating.
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Not applicable

Frequent "Connection Lost"

We are experiencing frequent connection loss to QlikSense server.  If we work locally (from within the company) there is no problem.

When working from outside, a popup window with the following message appears:

"Connection lost: Make sure that Qlik Sense is running properly.

If your session has timed out due to incativity, refresh to continue working."

We have set the session timeout in QlikSense Server to 30 minutes. But the connection lost happens after a minute.

In the developer console of ChromeBrowser, we can see the following entry:

Error from Engine:" error {target:WebSocket, isTrusted : true, currentTarget : WebSocket,eventPhrase : 2 bubbles : false, cancelable : false, defaultPreveted : false, timestamp :1433922, orignalTarget : WebSocket, explicitOriginalTarget : WebSocket, NONE : 0 }

The connection to wss://xxxxxx.com/resources/app/a4bdfb1b-71f2-42fc-83f2-53f4f7a...?reloadUri=https://xxxx.com-sense-app-a4bdfb1b-..../sheet/UCbAB/state/analysis was interrrupted while the page was loading.

Has someone discovered something similar before? What could be the problem?

21 Replies
Highlighted
Contributor III
Contributor III

this is a solution if you're using mashup and ticket, but you can interfere in the hub scripts as well.
this is indeed a bit annoying and the answers here did not help,

we're using the mashup option and it keeps disconnecting after 60 seconds of inactivity (not selecting anything in the model),

this is what we get:

"

An error occurred

Connection lost. Make sure that Qlik Sense is running properly. If your session has timed out due to inactivity, refresh to continue working.

"

luckily everything has a work around and a good one (:

so the deal is that as long as you provoke the web socket the connection will stay open, so just provoke it,

this is how its done:

create a variable in your model (Data Load Editor or in the bottom left of the sheet after pressing edit),

now create a KPI and put the variable in the kpi

last thing, put the qlik object on the top page and create a set interval

var qlikapp = null;

require( ["js/qlik"], function ( qlik ) {

qlik.setOnError( function ( error ) {

  $( '#popupText' ).append( error.message + "<br>" );

  $( '#popup' ).fadeIn( 1000 );

} );

$( "#closePopup" ).click( function () {

  $( '#popup' ).hide();

} );

//callbacks -- inserted here --

//open apps -- inserted here --

qlikapp = qlik.openApp('4287ca1c-9b53-45dc-afe2-55f8e69af7f2', config);

//get objects -- inserted here --

qlikapp.getObject('QV01','fkAQBG');

qlikapp.getObject('CurrentSelections','CurrentSelections');

//create cubes and lists -- inserted here --

} );

setInterval('KeepSessionAlive()', 5000);

function KeepSessionAlive() {

if (qlikapp) {

  //alert(getTime());

  qlikapp.variable.setStringValue('Current Time', getTime());

}

return false;

}

but do you really want to keep the socket open all the time?

this is an optimization question, if all the users use a named license then sure! but what if you convert some of them to Login Access Tokens? (you get 10 hours per month for each license)

this could be a waste of license time, so show some creativity, to my opinion 5 minuets of inactivity counted from the last mouse move on the page for login access user, and unlimited keep alive (until the window is closed for User access) is the best way to go.

this is a basic code for mouse move (i used it in qlikview i frame to keep the login alive):

var keepSessionAliveBool = false;

SetupSessionUpdater();

function SetupSessionUpdater() {

//...set the event that makes the keep alive

var container = $("#QvBody");

container.mousemove(function() {

  keepSessionAliveBool = true;

});

container.keydown(function() {

  keepSessionAliveBool = true;

});

CheckToKeepSessionAlive();

return true;

}

function CheckToKeepSessionAlive() {

setTimeout("KeepSessionAlive()", 30000); // // 1000 is every second

return true;

}

function KeepSessionAlive() {

CheckToKeepSessionAlive();

if (keepSessionAliveBool) {

  window.parent.postMessage("KeepSessionAlive", "*");

  keepSessionAliveBool = false;

  return true;

}

return false;

}

Highlighted
Contributor III
Contributor III

the root cause for this issue might also be load balancer (we use aws) and not qlik sense,

see:

Elastic Load Balancing Connection Timeout Management | AWS News Blog

console_elb_conn_settings_2.png

Highlighted
Contributor
Contributor

This was the solution for me as well. I was using AVG Antivirus for Mac. Once I disabled it, the error went away.

Thank you!! I've been dealing with this for weeks!

Highlighted
Contributor
Contributor

HI, all.

I am having the same "Connection Lost" problem.

Did you ever get a solution for that?

My connection is lost each 2-3 minutes….

Highlighted
Contributor
Contributor

yakir.manor‌ I am new to Qlik sense and facing same issue. It is possible to provide step by step instruction with snapshot?

Highlighted
Specialist
Specialist

I've had the same problem - change internet connection - if it works, you will have arguments for your IT department

Tomasz

Highlighted
Partner
Partner

Hello
I just solved the same problem.

Steps:
1) inside the QMC in the Virtual Proxy -> Advanced -> Host white list
Enter host address

2) You have to unlock the network proxy (not the Qlik sense one) so that it does not manage the address.

3) then verify that the browser uses the network proxy and not a manual proxy

Good luck

Highlighted
Partner
Partner

In addition to this, you would want to enable stickiness (unless this is a single node configuration). Within a multi-node site, stickiness is required to keep the session load balanced to the same node for the duration of the session. Without this, you are bound to receive connection lost errors all the time.

Highlighted
Partner
Partner

Hi Cocuzzan,

 

what exactly do you mean by "unlock the network proxy (not the Qlik sense one) so that it does not manage the address" ?

THX

 

Highlighted
Contributor
Contributor

I was experiencing the same error. I followed the instructions in the video below put out by Qlik Fix.

On the server where Qlik sense lives, I edited the proxy.exe.config file, changing the WebSocket ping interval from "0" to "60". I haven't received the error message since.

https://www.youtube.com/watch?v=EsHxJkaaMGw