Session gone after opening a new tab within Internet explorer / Google Chrome

We see a new tab with NEW session ID where the application expects the same session ID. Is this even possible within F5 to have same session ID within a new tab/window?

I would imagine this to be a browser vendor-dependent thing. What session ID are you referring to?

You're right about the first one. The session id is the Jsession ID produced by an IBM Websphere webserver.

So then the question is, does the client send the JSESSIONID from the first tab to the second tab? What persistence method are you using? Probably the best way to troubleshoot this sort of thing is to simply watch the traffic from the client's perspective. Load up HTWatch or Fiddler in the browser and watch:

1. When cookies are sent to the client

    

2. When the JSESSIONID is sent to the client

    

3. When the client sends back the JSESSIONID

    

4. What the client sends when it accesses the second tab

    

5 how the second tab responds to the client

When we investigate with firebug we see the JessionID what the client sends back stays the same when a new tab is openened.

Is Persistence in use? If so, which method please?

Interesting that this is about the forth issue I've seen this week around the JSESSIONID and new connections.

We've experienced with several ways of persistence. Cookie persistence and UIE persistance in combination with an irule. so far we've experienced same behaviour. It's possible a colleague of mine dropped a line as well.. :)

So let's eliminate a few factors. In the Fiddler traces you say the jsessionid stays the same. I'm assuming you mean in both tabs? If you enable cookie persistence, does that cookie change, or do you notice the client getting load balanced to a different server? What is different about the client's first request to the second tab and it's last request to the first tab? I'm talking about headers, cookies and anything else in the request payload. Last, what happens when the app fails? What does the server send to the client, and what is the last thing the client sends before the failure?

Just so it's clear, the second tab is to the same VS yes?

We've encountered something else where an icon should be displayed on the web page but isn't there. So the loadbalancer sends back a 302 error and does a redirect to the mainpage. This is on the same VS