Qlikview sessions time out on our users

[#1]

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

[#2]

Jason,

Thanks for the info.

I looked it up in the PDF, i don't see bug number 47449 ?

[#3]

I found an alternative to using POST by instead taking the code from Qva.OnDocumentClick.

That way qlikview will handle the refresh request to the qlikview server its own way and we get a much smaller sized response (300bytes vs 11kB) from the server than from the above suggestion. Or at least I did.

<script type="text/javascript">

var pingQlikView = function () {

     for(var d in Qva.binders){

          var a=Qva.binders;

          if(!a.Enabled){continue}

          a.Set("Document","click","",true)}

};

if (window.location.href.toLowerCase().indexOf("myreportname.qvw") >=0 ) {

     setInterval(pingQlikView, 1000*60*10); // Ping the server every 10 minutes

}

</script>

The script still has to go in the head part of opendoc.html. Also by checking if myreportname.qvw is part of the url we can limit the no-timeout refresh to specific reports. Other reports will timeout normally.

Quite possibly there is a better way of doing this as I am no javascript guru. I do like the idea of using qlikview's own javascript functions as much as possible though.

[Ricardo_Gerhard]

I didn´t find a change to users that using AJAX. When you set your document in tab Server, you can change the type of reload QVW file to your users.

I believe that this option should be saved, but it´s a WAD as I see.

[#5]

Hi acajohan,

Is this for AJAX? but this issue is happening also to the plugin. are you facing only in ajax?

[#6]

Hello,

We don't use the plugin, I assume this only works for ajax clients.

Also I am using this script for a slightly different need than the poster, namely timouts of documents authenticated through tickets (for both qv10 and qv11). But the end result should be the same in both cases ie no timeout.

/johan

[#7]

Any word on a new version release to allow adjustment of timeout settings?

[maggie50]

was this patch released?  I just reviewed the QV11 R4 beta release documentation and did not see it there but perhaps it was released earlier

[#9]

Hi,

Change the following config file.

..\QlikTech\WebServer\config.xml

Default:

----------------------------------------------------
  <QvsTimeout>60</QvsTimeout>
  <SessionCookieTimeOut>30</SessionCookieTimeOut>
----------------------------------------------------

[Whatever you want to set (in seconds)]

----------------------------------------------------
  <QvsTimeout>1800</QvsTimeout>
  <SessionCookieTimeOut>1800</SessionCookieTimeOut>
----------------------------------------------------

Hope this will help you.

Kaung Myat Tun

[#10]

Hi,

Change the following config file.

..\QlikTech\WebServer\config.xml

Default:

----------------------------------------------------
  <QvsTimeout>60</QvsTimeout>
  <SessionCookieTimeOut>30</SessionCookieTimeOut>
----------------------------------------------------

[Whatever you want to set (in seconds)]

----------------------------------------------------
  <QvsTimeout>1800</QvsTimeout>
  <SessionCookieTimeOut>1800</SessionCookieTimeOut>
----------------------------------------------------

Hope this will help you.

Kaung Myat Tun

[yujiyamane]

Go to QMC> System> Setup > Performance > Session.

Empty the field values of 'Possible Session Timeout' and 'Maximum Inactive Session Time'  (Empty means no limit)

Although the post is old, I had exactly same issue and resolved it with this way. Hopefully this could help someone at least.