"lightbulb432" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > I'm reading some book concurrency books that talk about potential thread > safety issues with HttpSession. Specific cases follow: > > - When the web container passivates an HttpSession while a user's request > modifies it
Should be rare, but I don't see anything in the TC code to prevent it from happening on edge cases. If someone can construct an example, I'd be more than happy to look into it. > - When the web container replicates an HttpSession while a user's request > modifies it I believe that with pessimistic locking, this shouldn't happen. But I'm not an expert on the TC replication code :). > - When multiple quick, successive requests from the same user access the > same HttpSession > > Could somebody explain how Tomcat deals with the first two, and what steps > web application developers need to take to avoid concurrency problems with > all three cases above? Is it guaranteed that the passivated/replicated > object is always a consistent view of the HttpSession? > > Thanks. > -- > View this message in context: > http://www.nabble.com/Concurrency-with-HttpSession-tf4403264.html#a12561600 > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
