----- Original Message -----
From: "Nic Ferrier" <[EMAIL PROTECTED]>
> >>> Gokul Singh <[EMAIL PROTECTED]> 11-Jan-01 7:59:19 AM >>>
>
> All I can say is that I'm doing almost exactly the same thing and it
> seems to be working for me.
>
> I put a hashtable in the session context and store sessions in that
> hash (by session-id).
>
> As I say - I don't seem to get any problems at all.
Thanks for confirming that the logic there seems to be correct.
Which version of tomcat do you use? or is it Paperclips?
As far as my limited analysis of the problem after peeking into the source
code of Tomcat3.2.1, is that it has switched to a facade pattern for
handling HttpSessions in 3.2.1 and the objects implementing the facade are
reused in different requests (as per comments in source). This I think it
must be doing by changing the HttpSession object this facade wraps around.
If this is the case, then even in your case it might give rise to random
behaviour. But I think Craig & the team are best ones to comment on this.
> Maybe post to the tomcat list on this? It sounds like a problem for
> Craig and the team.
I'll contact them. Maybe they can tell me better what happening inside
tomcat.
Regds,
Gokul
>
> Nic
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
