Disable Session Timeout

<session-config>
<session-timeout>-1</session-timeout>
</session-config>

Joonas Lehtinen: <session-config>
<session-timeout>-1</session-timeout>
</session-config>

Hi sir,

Thank you for your information . It was greately helpful to me.

Can I ask why you're doing this? Unless you restart the server occasionally, you will run out of memory since session objects never expire. Every time a user starts your app, a session gets created that never goes away (even if you only have one user, a single memory leak in your app will use all available memory eventually).

Can't you just store the application state in a database and retrieve it when a user loads the app? If you need some kind of 24 hour processing that keeps the app working, you can do that without keeping sessions around indefinitely.

Cheers,
Bobby

Hi all ,
You are correct sir. I already faced the memory leak problem not because of session timeout but some objects are not cleared properly.
Now i turned to default session time out .

Thank you all for valid information.

Joonas Lehtinen: <session-config>
<session-timeout>-1</session-timeout>
</session-config>

I also need to use this code, but I don't know where to place it... Can anyone tell me?

Thanks.
Hugo

I use this in my web.xml of Vaadin 7 project.

<session-config>
        <session-timeout>1</session-timeout>
</session-config>

But the session is not closing after a minute.. any ideas??

I have a background thread running in my app that gets some information from the browser. Will that be a problem?

Update:
Even I stopped the thread and ran my app. Session is not expiring.. :-(

Wait few more minutes ;-). From my experience, a session expires about 3-7 minutes after the time is set for a timeout.

Agata Vackova: Wait few more minutes ;-). From my experience, a session expires about 3-7 minutes after the time is set for a timeout.

Nothing happens Agata... I have waited for more than 30 minutes..

And also I use ICEPush in my application. Will that be a reason?

hi
Sometimes users can run real time chart for example(using timeline) and they might want to visit the page a day or 2 later and see the results.
Instead they see "Session Expired

Disable session timeout and set cookie max age, so that session cookie will be kept in the browser after it is closed, (normaly session cookie is session scoped and disapears after browser restart.)

​        <cookie-config>  
            <max-age>720000</max-age>  
        </cookie-config>  
    </session-config>

this above piece of config - where exactly should I put it?
 

Put it inside your web.xml file. At the session-config section.
here you can find example. And here the docs.

I dont have web.xml. Can I use annotation for that?
 

VaadinSession.getCurrent().getSession().setMaxInactiveInterval(300); 

in

init(VaadinRequest request) {
          VaadinSession.getCurrent().getSession().setMaxInactiveInterval(300); 
           ...
} 

as far as I know, there is no annotation parameter for that. 

Julian M: I dont have web.xml. Can I use annotation for that?

 

Thanks. is this set in any UI component? all all of UI components. 
each Vaadin session for one UI component? 

I still cannot find any combination of techniques that will prevent rapid session timeout on a "idle" UI.  Wth?

I have settings in the code and in web.xml - nothing seems to have any effect whatsoever, and the timeout is fast (like only a few minutes of "idle" time).  I say "idle" because I am generating activity on a thread that is being dispayed on the UI - I just am not clicking or typing.  The scenario is an active "Dashboard" that gets updated every 5 seconds.  User will only interact when needed, but the dashboard is intended to run continuously until stopped, exception warrants auto-stop or it literally crashes somewhere.

How the heck do I keep this thing alive?  At this point, the application is literally useless because of this BS timeout.

What am I missing or is Vaadin the wrong tool for this?

c

Benjamin Huygir: I still cannot find any combination of techniques that will prevent rapid session timeout on a "idle" UI.  Wth?

I have settings in the code and in web.xml - nothing seems to have any effect whatsoever, and the timeout is fast (like only a few minutes of "idle" time).  I say "idle" because I am generating activity on a thread that is being dispayed on the UI - I just am not clicking or typing.  The scenario is an active "Dashboard" that gets updated every 5 seconds.  User will only interact when needed, but the dashboard is intended to run continuously until stopped, exception warrants auto-stop or it literally crashes somewhere.

How the heck do I keep this thing alive?  At this point, the application is literally useless because of this BS timeout.

What am I missing or is Vaadin the wrong tool for this?

c

P.S.  Test environment is a local Tomcat 8 server - usually just running via Eclipse so I can debug.  Is that having an effect?  Are there additional Tomcat or JVM settings I have to provide?

Joonas Lehtinen: <session-config>
<session-timeout>-1</session-timeout>
</session-config>

Seems to have zero effect in Vaadin 8 / Tomcat 8.5 configuration.  I wish it was this easy.
 

Wow - that actually seems to be working.  No other value positive or negative seems to do anything (like I had a value of 7200 in there which should be at least hours but if it's minutes means 5 days - and that did nothing at all).  The zero value must be a "magic number" that does more than an actual value.  Thanks!  Finally.

Benjamin Huygir: Seems to have zero effect in Vaadin 8 / Tomcat 8.5 configuration.  I wish it was this easy.

Hi Benjamin,

If you are using Tomcat 8.5, according to the specs, you should specify a value of 0 for an unlimited timeout.

Benjamin Huygir:
Wow - that actually seems to be working.  No other value positive or negative seems to do anything (like I had a value of 7200 in there which should be at least hours but if it's minutes means 5 days - and that did nothing at all).  The zero value must be a "magic number" that does more than an actual value.  Thanks!  Finally.

edit: not certain what happened to my original post, but I am glad that setting the value to 0 worked in your case.

BR,
Goran