Ok. One other thought that's burned me once -- servlet instances are recycled between requests without resetting any of it's field members. The next request gets it exactly as the one before left it. That means you should either avoid field members in favor of method parameters + method local variables or be sure to reinitialize them before processing a new request.

--David

Srinivas Gunturu wrote:

All 6 of us are logging simultaneously from different machines.

The way, we store the user object in session is inside LoginAction class and 
not inside the jsp.

       session.setAttribute(Constants.USER_KEY, userInfo);




[EMAIL PROTECTED] 07/14/05 10:34 AM >>>
Hi,
It never happened to me and it will not happen also unless there is some serious bug in ur code.
Are you six people trying to login simultaneously from different machines?
Or trying to login from same system one after another from same system?
If it is the second case, then it copuld be the problem with browser cache. Clear cache and check. If it is the second case , check what is given for the "scope" attribute of the user bean (assuming you used <jsp:usebean> or something similar). If scope is given as application instead of session (or request) this could happen. regards Srikanth On 7/14/05, Srinivas Gunturu <[EMAIL PROTECTED]> wrote:
Hello All,

I have been fighting this session mix-up problem in our application which is very easily reproducible.

Environment:
Tomcat 5.0.9
Struts 1.1

Upon user login, we create a user bean object and store on user session. When 6 of us tried to login separately using our own logins, we could see our sessions get mixed up and also seeing other user's name in welcome greeting.

I have tried migrating to Tomcat 5.5, tried turning of Tomcat session persistence, tried making user object serializable.

Still no luck. Any idea?

TIA,

Srinivas




---------------------------------------------------------------------
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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to