On Nov 19, 8:16 pm, David Pollak <feeder.of.the.be...@gmail.com> wrote: > On Wed, Nov 18, 2009 at 10:28 PM, Marius <marius.dan...@gmail.com> wrote: > > That makes two of us David ... > > > The thing is that during my debugging there was no session destruction > > and I traced this right in the guts of SessionMaster. > > I went further and it seemed that the sessions were destroyed at the Servlet > Container level.
I can't say I grok the lift request cycle, but I looked into the jetty part and this is what I think happens: At some point getCookies is called (by Lift) on a HttpServletRequest that seems invalid (ie empty). This causes the internal state of the request object to be marked "cookies are parsed". Just there are no cookies since the request is empty. Jetty recycles the request objects, so later when a request comes in that reuses this request object and it tries to fetch the session cookie, it sees that cookies are already parsed but can't find the session cookie (there are none) and thus creates a new session. Why the request object is not re-initialized for the new request I don't know...also it doesn't really explain the error on Tomcat Not sure if this helps...:-) /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=.
