This content has been marked as final. Show 5 replies
I have the same problem.
I got a java serverside with a flex client. So at serverside i created a class that extends AbstractBootstrapService (so it is loaded as Flex Service from services-config.xml) and it implements FlexSessionListener interface - listens for sessions created and closed. But i feel a real lack of knowlege how flexSession works and how to properly configure it.
At the moment the session destroys (and my SessionListener class performes all its *user logged off* work ) 5 minutes after the browser is closed, and i have no guesses how to make it faster/
ah, got it, just a <session-config> section in WEB-INF/web.xml
You saying your listener method gets called 5 mins after the Logoff?
yes, if the browser just closed, without calling *log off* method, then i listen to destroying sessions, get client id from it and do log off for this client (clearing serverside data on it and so on)
i tried to tune timeout setting at <session-config> in web.xml - but the session still dies only 5 minutes after the browser is closed.
You are lucky with your 5 minutes. I just tried with my environment (LCDS is deployed on Tomcat 5.5), keeping all the default settings, killed my browser after connecting (I do have both HTTP and RTMP connections created), and noticed the following:
- the RTMP session was instantly invalidated
- the HTTP session was kept alive for exact 30 minutes, then it was invalidated (and at that point the FlexClient was also invalidated, as it contains no more sessions).
I'm looking at ways to set that session timeout value now, to be less than 30 minutes.