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.
My application is facing one problem, when the user uses http://myapp.mycompnay.com, the session is timing out while navigating back from other other company applications. But this problem is not happening always if the user uses with 'www' before my application. We need to retain the session as the user can login in one application and navigate back and forth to all other company apps. The problem is happening only when the user clicks on browser back button to comeback to my application. The authentication module is common in all the applications, and rest of the applications do not have this problem.
I use SunOne6.1 and Websphere application server. Does anybody have this kind of problem? since login module is same in all apps, do you have any idea whether this problem is related to SunOne or Websphere or Plug-in configurations?
Is it possible that as you navigate between each application the JSESSIONID is changing (being over written) . This assumes the applications are hosted in different JVMs?
A scenario like this
- Login assign JESSIONID:12345
- Navigate around your application no problems
- Navigate to other company application , this applications over writes JSESSIONID in browser . Browser now has JSESSIONID:54321
- From other application navigate back to yours. Browser sends JSESSIONID:54321 your app doesn't recognise this jsession and your req.getSession returns null ?