Tomcat 5.0.28. >>> [EMAIL PROTECTED] 10/4/2005 3:34:31 AM >>> What's your container? I saw this behaviour on older resin implementations, it was obviously a bug, that in some sequence of requsts the session got mixed, B got A's session, but only for one request, after that it had it's own session. Try to log out the session id and the value of the jsessionid cookie to find out if its the right session.
regards Leon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
