You have some cross-talk somewhere in your code, by the sound of it.
Take a look at any code that touches the session; you probably have
something somewhere that's at the wrong scope (in application scope when
it should be session/request, a Spring bean accidentally configured as
singleton scope, ...).
Without access to your source code, it's impossible to say much more
than that but if you can narrow it down and post the code that's causing
the problem, someone may be able to explain why it's not working as you
expected.
L.
MARollins wrote:
I am running everything from one machine, but access the app from different
browsers in order to get different sessions (ie IE and Firefox). I have
tried the second user from another machine and it didn't make any
difference.
The app also uses Spring, but I have configured this to give me a new user
object as required rather than the default singleton, and I'm happy this is
working.
When logging in for the second user, I can see that the session map is empty
for the new user's session, then session.put is called with the new user
object, and this seems OK.
If I then call an action using the first user and access the session map,
hey presto, I've got the user object from the second user.
Server is Tomcat 5.5 and Struts is v2.
newton.dave wrote:
--- MARollins <[EMAIL PROTECTED]> wrote:
I'm having a problem whereby objects saved on the
Session are visible to other sessions.
For example, the login page saves a new User object
on the session using session.put (I have a base
class
for all my Actions which implements SessionAware in
order to be able to access Session variables). When
a
second user logs on, the first user then sees the
second user's ID. It's almost like we're writing to
the application rather than the session.
Any ideas where I'm going wrong?
Not with so little information to go on.
Is the "second user's login" happening from a
different machine and / or different browser?
d.
---------------------------------------------------------------------
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]
