Right. But that's exactly what the timer is for. It keeps the app alive so long as the user is actively working in it. Otherwise, they could be in the middle of something and suddenly be logged out. You could set the timer for a shorter period of time, say 10 minutes. But, from what your describing, the countdown timer is doing exactly as it was designed.
You could execute custom JS and force the session to end at certain time intervals. I'm worried you'll have some irritated users.
Here's some of the JavaScript used with the timer (located in netweb.js):
Called when the user logs in (in PageFooterTag):
startCountDown('& int(p_web.site.SessionExpiryAfterHS/100) &',"'& clip(p_web.site.LoginPage) &'","countdown");
Generated:
startCountDown(3600,"LoginForm","countdown");
In netweb.js -------------------------------------------------------
var cnt=0;
var tcnt=0;
var fcnt='';
var icnt='';
function countDown(){
hh = parseInt( cnt / 3600 );
mm = parseInt( cnt / 60 ) % 60;
ss = cnt % 60;
var t = hh + ":" + (mm < 10 ? "0" + mm : mm) + ":" + (ss < 10 ? "0" + ss : ss);
jQuery('#' + icnt).html(t);
cnt -= 1;
if (cnt ==0){
window.open(fcnt,'_top');
} else {
setTimeout("countDown();",1000);
}
};
function resetCountDown(){
cnt = tcnt;
}
function startCountDown(t,f,i){
if (t){
tcnt = t;
}
if (f){
fcnt = f;
}
if (i){
icnt = i;
}
cnt = tcnt;
countDown();
};
Topic: Session expired reseted ... (Read 7339 times)