Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Session timeout problem

 
Ranch Hand
Posts: 173
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi
I am getting a session timeout problem on weblogic 6.1- Sometimes it expires even after a few minutes of login. I have the following tag in my web.xml


Advice plz on why the timeout is unpredictable!

Thanks
GUL
 
Ranch Hand
Posts: 624
IntelliJ IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
One possibility is where are you putting that setting in your web.xml file? The order of placement of elements in the deployment descriptor (i.e. the web.xml file) is critical. Is the session-config element placed in the correct order (as defined in the DTD) in your web.xml? The version 2.3 DTD defines the order of elements as being:



Verify that your session-config is in the correct order as compared to the other elements of the web.xml file. Since I do not use it, I'm not sure how Weblogic handles an invalid deployment descriptor - it may just ignore an out of place element rather then generating an error. Then again it may be putting an error message in your logs.
[ June 03, 2004: Message edited by: Mark Vedder ]
 
Gul Khan
Ranch Hand
Posts: 173
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator


The descriptor looks ok to me.. It is more troublesome coz it does not happen all the time and all i see in the log is the session is null/invalid/timeout.
I will appreciate any kind of help.
Thanks for replying

Gul
 
Mark Vedder
Ranch Hand
Posts: 624
IntelliJ IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sorry then, for I am out of ideas. The only other thing I can suggest is to see if you can increase the verbosity of your logs. Again, I am not familiar with Weblogic since I use Sun ONE servers. But with most servers you can increase the log verbosity.(It's just a matter of finding where that config setting is.) Maybe doing such will give you some more information that will help. If I can think of any other ideas, I'll be sure to come back and post them. Hopefully someone else will have an idea. Good luck.
 
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
session timeout specified in web.xml is treated in minutes by the container. so logically session should expire after 500 minutes(According to your configuration).

besides session configuration in web.xml, are you using Session.invalidate() method on some conditions ?
 
Ranch Hand
Posts: 1211
Mac IntelliJ IDE
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You might want to check whether a call to session.setMaxInactiveInterval() is being made anywhere. Also, you could use session.getMaxInactiveInterval() on suspicious pages to get the session time out set for that page.
 
    Bookmark Topic Watch Topic
  • New Topic