Matthew Woodward said the following on 08/17/2009 06:52 PM: > Peter J. Farrell wrote: >> FYI, the same thing happens with JRun and CF -- if the session >> timeout exceeds the JRun max session length -- JRun wins. It's the >> inherit nature of servlets. Probably good to note. > > JRun's default is also 30 minutes (this MAY be something specific in > the servlet spec even), but I wonder if in the CF bundled version they > set it to the max value, which from what I can tell is 24 days. Did some snooping and in the a standard install jrun-web.xml there is not session-timeout node, but a notice:
session persistence needs to be disabled due to our classloader setup In the JRun docs, this is stated: If you set session-timeout to 0 or any negative value, Jrun does not time out or persist sessions after any period of inactivity. It seems plausible that CF is expiring the sessions by itself internally instead of relying on the application server to do it for us. However, that totally changes if you deploy CF on Tomcat (then Tomcat takes precedence). .Peter --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
