Forum Discussion
NimbostratusJSESSIONID LTM
I'm experiencing strange behavior between my F5 and the backend WebSphere Application server 7. If a user opens a new tab (help or printing PDF) and went back to the first tab the user experience a session timout.
The application is using a JSESSIONID and we use for loadbalancing a session (HTTP COOKIE INSERT). I think the above method is not the right one.
When I look at knowledgebase article sol7392:Overview of universal persistence, i think that's the solution for my problem. To use the JSESSIONID to loadbalance the web servers.
If some one has experience with the above problem please leave a message.
Greetings Peter
4 Replies
Peter_L_71637Extra info : We are using TMOS 11.4.0 HF3
What_Lies_Bene1Cirrostratus
Thanks. So, it's a single VS serving all the different types of content? No iRules applied that might be having an affect? Cookie should work just fine.
- Eric_St__John
Employee
Have you tried similar steps to reproduce the problem with different browsers? Some versions of IE will open tabs in a separate process, causing similar issues.
Regards,
Eric
- Kevin_Stewart
If I may add, the best thing you can do is to first find out why the application is failing. If you suspect that cookie persistence is the reason, then you need to look at the traffic between the client and app, and the client and the next open tab (help or PDF print) and see if the persistence cookie changes and/or goes away. I suspect you can still fix this method if it is the problem. Otherwise, if JSESSIONID is the route you want to take, you have to ensure again that the JSESSIONID is in EVERY request to the VIP, both for the app and the next open browser tab.
