This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I deploy a domain in my pc,and run well. at the meaning time ,I change the PC TIME from 2005-11-16 to 2006-1-16, then ,all the jsp pages using SESSION Object was wrong ,because the session is null.
so I guess maybe the server compare the new time to the beginning time,thought the session has last for 2 monthes, so the session is invalid . but i changed the tag <session-timeout> in the config.xml of weblogic server,restart the server,it doesn't work.
What do mean by saying, "It didn't work"? Actually when you stop the server and start it again then it should create some new sessions for users. It should work fine with the new system time.
You change the session time-out value to __ ? Moreover, setting value to -1 means session would never expire.
Joined: Oct 26, 2002
sorry about my explanation. "it doesn't work" means after I changed <session-timeout> value to -1, and the weblogic server restart too.And I repeat the above operations: first login in the web site,the session is not null surely,then change the system time ,the jsp pages exception happen. what i thought is maybe one of the two reason can explain these scene: 1) the value of -1 for <session-timeout> cannot solve the problem in my case. 2) when i login in web site in 2005-11-16,the session is taged the timestamp or unique id somewhat by weblogic server, and i change time to 2006-1-16,although the session.isvalid() return true,but the session id changed??? (it seems the reason is eisegesised)