I'm not sure what you are trying to tell me.
If you are wondering if the monitor bean works, the answer is yes it does.
If I do what you suggest:
// Got user. Do they already have a session?
if ( !monitor.containsKey(user) ){
// There's _NOT_ an old session for this user - invalidate it
HttpSession oldSession = (HttpSession)monitor.get(user);
oldSession.invalidate();
}
Then, I get:
java.lang.NullPointerException
at checkLogin_1._jspService(checkLogin_1.java:135)
at "oldSession.invalidate()"
It seems that when tomcat tries to invalidate() a session. I get an
error that says the session is already invalidated. But, I know the
session is not already invalidated.
Is this a tomcat bug?
Thanks,
Rick
Dominic Parry wrote:
>> if( monitor.containsKey(user)){
>>
>
> Check what if this returns true of false for "has a session". Try
>
> if !(monitor.containsKey(user)){
>
> see if the case where the user has no session now works.
>
> Hope this helps.
>
>
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
