Sanjay Prasad Prasad commented on Sep 10, 2012

Re: How to keep XPages Session Alive without using Extension Library

where exactly i need to put this code.....

Sanjay Prasad Prasad commented on Sep 10, 2012

Re: How to keep XPages Session Alive without using Extension Library

where exactly i need to put this code.

Sanjay Prasad Prasad commented on Sep 10, 2012

Re: How to keep XPages Session Alive without using Extension Library

where exactly I need to put this code.

Paul Thomas Lan2Lan commented on Mar 23, 2012

Re: How to keep XPages Session Alive without using Extension Library

Pasted in code.

After a while the user login page appears.

Domino 8.5.3 using Multi-Server SSO

Robert F Harwood commented on Jan 12, 2012

Re: How to keep XPages Session Alive without using Extension Library

1/12 Checked comments. no action needed

Ryan Buening commented on Apr 4, 2011

Re: How to keep XPages Session Alive without using Extension Library

@Joacim - Thanks for clarification.

@Peter - Thanks for this tip. I had set a session and application timeout set at 540/240 minutes respectively and users were still losing their session variables after leaving the page dormant for 20 minutes or so. This seems to help.

Peter Arndt commented on Apr 4, 2011

Re: How to keep XPages Session Alive without using Extension Library

@Joacim, thanks for your improvement, I upgraded the document.

Joacim Boive commented on Apr 3, 2011

Just paste.

@Ryan - Just paste it. The setTimeout-function handles the calling.

Ryan Buening commented on Apr 1, 2011

Re: How to keep XPages Session Alive without using Extension Library

Do you have to call this script onload somewhere, or is this just paste and play?

Joacim Boive commented on Apr 1, 2011

Re: How to keep XPages Session Alive without using Extension Library

Running 8.5.2 FP1 with a default setup: xsp.session.timeout returns an empty string.

This causes an infinite loop of AJAX requests flooding the browser.

There's an easy fix.

Change this:

var sTimeoutSec = (parseInt('#{javascript:context.getProperty("xsp.session.timeout")}') * 60) - 30;

To this:

var sTimeoutSec = (parseInt('#{javascript:context.getProperty("xsp.session.timeout")}' || 30) * 60) - 30;

Now, if timeout isn't set in the xsp.properties it will fall back to the default 30.