About Session Timeout

answered 2012-05-31 15:09:46 +0800

janfran3
15

I think the delay to fire event is too long, so the session timeout occure anyway.

janfran

answered 2012-06-01 15:17:34 +0800

zippy
504 ● 1 ● 2

You need this

package cl.zippy;

import org.zkoss.zhtml.Messagebox;
import org.zkoss.zk.ui.Component;
import org.zkoss.zk.ui.event.Event;
import org.zkoss.zk.ui.event.EventListener;
import org.zkoss.zk.ui.util.Composer;

public class DoNothing implements Composer{
	 public void doAfterCompose(Component comp) throws Exception {
	        comp.addEventListener("onTimer", new EventListener() {
	            public void onEvent(Event event) throws Exception {
	                //Messagebox.show("alive");
	            }
	        });
	    }

}

and

<timer id="timerKeepAliveSession" running="true" repeats="true" delay="600000" apply="cl.zippy.DoNothing"/>

answered 2012-06-04 04:29:28 +0800

rdgrimes
735 ● 7

updated 2012-06-04 04:39:59 +0800

Actually, if I recall correctly, you do not actually need the DoNothing code Zippy suggested.

If memory serves me, the reason you are timing out in your original configuration is because your timer delay was for 6 million ms, which I believe is 100 minutes. I know for Tomcat, the default session timeout is 30 minutes unless you override it in the web.xml. So, your zul timer delay and repeat was never reached at the 100 minute mark, but instead timed out per the default web.xml session timeout. In other words, if your server container defaults to a 30 minute timeout, then by simply changing your delay to 600000, instead of 6000000, it would take effect before your session time's out.

See your original post. You had it at 6000000. In Zippy's "fix" post, it was changed to 600000. That is what, in fact, fixed the problem. The DoNothing code indeed does nothing.

If reducing the zul timer delay does not fix it, then specify, in your web.xml a session timeout that is longer than the zul timer delay, such as:

<session-config>
    <session-timeout>30</session-timeout>
</session-config>

The web.xml uses minutes as the value, while the zul timer delay uses ms. So, careful of the difference.

The DoNothing code was suggested by ZK only for versions 5.0.6 and earlier, just as an FYI.

Ron

answered 2012-06-04 07:35:58 +0800

gekkio
899 ● 1
http://gekkio.fi/blog

One thing that hasn't been mentioned yet: you need to explicitly activate a setting in zk.xml or onTimer events will not keep the session alive.

Ron, your comments on the session timeout are definitely the core problem here, but I'm still not sure about the dummy onTimer listener.

If we look at ZK source code where the onTimer event is declared:

addClientEvent(Timer.class, Events.ON_TIMER, CE_DUPLICATE_IGNORE);

It is defined with the flag CE_DUPLICATE_IGNORE, but not with CE_IMPORTANT. If CE_IMPORTANT is not used, the client will not send events to the server if there are no listeners. This means that if the dummy listener is not used, the server will never see timer events and the session will time out.

It's possible that there's some special code for onTimer events, but to me it seems that an onTimer listener is needed.

answered 2012-06-04 14:53:18 +0800

rdgrimes
735 ● 7

I would refere to this link (http://books.zkoss.org/wiki/ZK_Developer%27s_Reference/UI_Patterns/Session_Timeout_Management). The use of the timer listener is taken from documentation for 5.0.6 and earlier. The newer documentation that I cited mentions nothing of it.In fact, the only thing I have configured in my project is in zk.xml, web.xml, and then the timer in the .zul page. I don't use a timer listener, and it functions just the way I want.

Here's how I have it:

ZK.XML

	<session-config>  
		<timer-keep-alive>true</timer-keep-alive>
	</session-config>

WEB.XML

	<session-config>  
		<session-timeout>30</session-timeout>
	</session-config>	

*.ZUL

                     <timer id="timerKeepAliveSession" repeats="true" delay="600000"/>

That's it, nothing more, and it doesn't timeout on me.

answered 2012-06-04 14:57:31 +0800

rdgrimes
735 ● 7

One more thing. You don't mention much about your environment. But, be aware that timeouts can exist at multiple levels: your desktop browser, your WAF (if you have one in place), the war container (Tomcat, Websphere, etc.), your PIX (again, if you have one).