[chandler-users] Chandler Server timeout...

[Travis Vachon]

Hi Sam

You can configure the client side timeout  in cosmo.properties by  
setting the ui.uiTimeout to an integer. I'm pretty sure -1 should  
disable it completely, but I'm not sure that's particularly well tested.

If that property isn't set, the client side timeout gets set to the  
same value as the session timeout. This means that if you manually set  
the client side timeout to a different value, you'll get "strange"  
behavior once the session timeout has expired, ie, being able to  
interact with the ui and create/modify/delete events, but being forced  
to re-login once you reload the page.

To avoid this weird behavior you can just configure the session  
timeout. Setting session timeout is a standard Tomcat administrative  
task. I know it can be accomplished within the Cosmo war in web.xml,  
but would guess it can also be done at the container level, though I  
need to do some more research to figure out exactly how.

Let me know if that works, and feel free to stop by #cosmo on  
irc.freenode.net for high bandwidth help.

-Travis

On Feb 1, 2008, at 7:41 AM, Sam Halliday wrote:

> Hi all,
>
> Is there any way to turn off client time-outs in the Chandler web  
> app? It's really really annoying to get booted off. I like to keep  
> my browser open on Chandler Server and look at events periodically,  
> but almost every time I look I've been kicked off and have to login  
> again.
>
> -- 
> Sam
>
> http://fommil.me.uk
> http://javablog.co.uk
>
>
> _______________________________________________
> chandler-users mailing list
> chandler-users at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/chandler-users