This could be a session crossover issue. Here's IBM's documentation on it: "In rare situations, usually due to application errors, session data intended for on

This could be a session crossover issue. Here's IBM's documentation on it: "In rare situations, usually due to application errors, session data intended for one client might be seen by another client. This situation is referred to as session data crossover. When the DebugSessionCrossover custom property is set to true, code is enabled to detect and log instances of session data crossover. Checks are performed to verify that only the session associated with the request is accessed or referenced. Messages are logged if any discrepancies are detected. These messages provide a starting point for debugging this problem. This additional checking is only performed when running on the WebSphere-managed dispatch thread, not on any user-created threads." http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-express-dist&topic=rtrb_httpsessprobs http://www14.software.ibm.com/webapp/wsbroker/redirect?versi...