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.
Hi, We are facing a strange problem regarding session implementation. We have set a session timeout of 25 min but some of the users (ONLY SOME)of our site are getting timed out in less than 25 mins . We are using WebSphere 3.5.3 and Netscape Enterprise Server .We have overridden the default timeout provided by WebSphere by using setMaxInactiveInterval() method of HttpSession class. We are using cookies for session management and on extensive debugging of our problem , we found that at some of the client's browser , our session cookie(created by WebSphere) is not being created altho' the user has cookies enabled on his browser's settings. I know one of the solution to this problem is to go for URL rewriting for session implementation but we don't want to go for this implementation because it has some inherent drawbacks,moreover it would require a huge effort on our part because our site is pretty big. Any thoughts on this problem or anybody else has also faced this kind of the problem.??? Thanks in advance Sudhakar
Hi, I've got this trouble using Tomcat 4.0 . The sessions references sometimes simply desapeared or get invalidated nearly than it should be. The solution was implement a session manager that is executed by a Thread, and takes care everything about sessions in each 2 minutes. I know it's hardous, but it was the only thing that worked. Claudio Gualberto
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: strange problem regarding session management in websphere 3.5.3