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 ]
posted 16 years ago
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
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.
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.
The future is here. It's just not evenly distributed yet. - William Gibson
Sonny GillLinkedIn Tweets