getThreadLocalRequest().getSession() gives you the real/actual HttpSession of your application server. As long as you visit page a and page b from the same browser instance you have the same session. So you probably have a different problem.
I don't know your servlet code but keep in mind that you have to work with session attribute values in a thread safe manner. Session.getAttribute() and Session.setAttribute() are thread safe but your servlet is not as it can be executed by several threads in parallel (depending on the number of parallel requests). Also check that you do not have multiple session cookies for the same domain and path for some reason and that, if you use clustering, your session replication is working correctly. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Kb9YAVdZ-AMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
