• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

session-config in web.xml

 
Amirtharaj Chinnaraj
Ranch Hand
Posts: 241
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi guys

i know that we have to use this stuff for maintaining session in a web application in web.xml

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

i want to know what will happen if didnt configure this element in the web.xml is that container will provide any default values for this, also i want know the different behavior when this element is not set in web.xml

but iam able to deploy the application without this element in the web.xml
with jboss 4.0

looking for your replies
regards
amir
 
Christophe Verré
Sheriff
Posts: 14691
16
Eclipse IDE Ubuntu VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The Servlet Specification(2.4) tells :
If this element is not specified, the container must set its default timeout period.. Refer to it whenever you have such a doubt.
 
sanjiv tuli
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Setting session timeout through the deployment descriptor should work - it sets the default session timeout for the web app. Calling session.setMaxInactiveInterval() sets the timeout for the particular session it is called on, and overrides the default. Be aware of the unit difference, too - the deployment descriptor version uses minutes, and session.setMaxInactiveInterval() uses seconds.

So

<session-config>
<session-timeout>60</session-timeout>
</session-config>
sets the default session timeout to 60 minutes.

And

session.setMaxInactiveInterval(600);
sets the session timeout to 600 seconds - 10 minutes - for the specific session it's called on.

This should work in Tomcat or Glassfish or any other Java web server - it's part of the spec.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic