On 21.09.2009 00:45, Christopher Schultz wrote: > Theparanoidone, > > On 9/18/2009 11:45 PM, Theparanoidone Theparanoidone wrote: >> Thank you; that's pretty close to what I am looking for (as it relates to >> mod-jk): > >> As a follow up question, it seems safe to assume that tomcat will >> receive the JSESSIONID's in the appropriate order... however, in our >> struts application there appears to be a limited way to retrieve the >> session: > >> pseudo code: >> map m = ActionInvocation ai.getInvocationContext().getSession() > >> 1) Is it safe to assume that the above call will return the "more" specific >> JSESSIONID? > > Struts will get whatever session Tomcat hands to it, so this is really a > Tomcat question: the current version of Tomcat will take all available > JSESSIONID cookie values and give you the one that matches a > currently-valid session. If none matches, I think you get an arbitrary > session id returned from request.getRequestedSessionId and if you call > getSession(true), you'll get a new session created.
... and in the current implementation they should be tried in the order they are received from the client. Although I didn't find anything in the SPEC which mandates or suggests that. If all fail, request.getRequestedSessionId() should return the value of the last cookie, i.e. the least specific. "Should" in the sense that's what I expect from current TC 6.0.x code, not in the sense of being the best choice. Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
