Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Qlikview sessions time out on our users

Friends,

Please help us resolve this problematic issue.   Our Qlikview sessions are timing out in under an hour, though our server settings are set much higher (at least we believe we did it correctly).   We are on Qv 11 SR1 and all seems like all is working fine.   We are not using IIS, we are using Qlikview's web server.   Users use the Ajax client to connect to the server and view documents.  

When the sessions time out, users lose their selections which causes problems in longer meetings where the QV document is only referred to intermittently. 

We've set the following in QVS:  System -> Setup->Qlikview Servers->Performance

  • Maximum Number of Concurrent Sessions: 5000
  • Maximum Inactive Session Time: seconds:  10800 seconds
  • Possible Session Timeout: seconds 10800 seconds
  • Maximum Total Session Time:  (blank)seconds

We've set the following in QVS on the Document in question:   Documents -> User Document -> select the document - >  Performance

  • Maximum Number of Concurrent Sessions: (blank)
  • Maximum Inactive Session Time:  14400 seconds
  • Document Timeout:  240 minutes

Can anyone recommend a setting where we might have overlooked something?   

Thank You,

David Fields

479-549-7764

29 Replies
alexpanjhc
Specialist
Specialist

how /where do i check out the defects?

Is there a defects list in the community? or you went through the documents?

chriscammers
Partner - Specialist
Partner - Specialist

Good Question,

I knew about it because I filed a support case to investigate the issue.

I have not seen a searchable defect list.

Hmm, I bet that would make a good qlikview app

Not applicable
Author

Chris - has there been any update on the timeout issue? Thanks

zekazak
Creator
Creator

Hi Chris,

Did you find a patch to fix this (defect 47449)  or are you still waiting for it?

Best Regards,

~Sergejs

Bill_Britt
Former Employee
Former Employee

There has not been a patch issue for that.

Bill

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
zekazak
Creator
Creator

Hello,

Have anybody found a solution for this? Is there any new ideas  on how to fix this?

Best Regards,

~Sergejs

Not applicable
Author

You can modify the opendoc.htm file (in <QlikView install dir>\Server\QlikViewClients\QlikViewAjax) to contain a script that makes an AJAX call to prevent the session from idling. Changing opendoc.htm isn't supported by QlikTech, though. The below script should be added to the <head> section of opendoc.htm; it pings the server every 20 minutes for 2 hours. Alternatively, you can use the setInterval() function instead of setTimeout(), and this will ping the server forever... the downside is it will prevent all sessions from becoming idle, which might not be something you want.

    <script type="text/javascript">

        /* This script will ping the server every 20 minutes (for 2 horus) after opening the page to prevent a session from

          from going idle, which normally will happen after 30 minutes due to a bug. This will give the

          user 150 minutes to be idle after opening the report. -- jcoon 2012.11

        */

        var pingQlikView = function () {

          var str = '<update></update>';

          $.ajax({

            type: 'POST',

            url: '/QvAjaxZfc/QvsViewClient.aspx?mark=' + qva.Mark + '&view=' + qva.View + '&host=' + qva.Host + '&slot=',

            processData: false,

            data: str,

            dataType: 'xml'

          });

        };

        setTimeout(pingQlikView, 1000*60*20); // Ping the server at 20 minutes after open

        setTimeout(pingQlikView, 1000*60*40); // Ping the server at 40 minutes after open

        setTimeout(pingQlikView, 1000*60*60); // Ping the server at 60 minutes after open

        setTimeout(pingQlikView, 1000*60*80); // Ping the server at 80 minutes after open

        setTimeout(pingQlikView, 1000*60*100); // Ping the server at 100 minutes after open

        setTimeout(pingQlikView, 1000*60*120); // Ping the server at 120 minutes after open

</script>

Not applicable
Author

Hello,

I have the same problem, but we are using plugin. V11 SR1.

When this happen, there's no reloading or other activities on the server.

only few users are connected to the server.

CPU and RAM usage is below half.

I had a look into the server event log. and i saw this.

" The QlikView Server service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 10 milliseconds: Restart the service. "

How do we get update about the news?

Thanks.

Not applicable
Author

Hi All,

There's a new release on build: 11440.


Did anyone try yet? it's said to address this issue.

Not applicable
Author