Based on what I've done in the past, you need to put the session-config in the conf/web.xml in the tomcat dir. Be sure that there are no duplicates -- I can't remember if the first person to set it wins or the last -- but I've accidentally had two in there before with different values.
.pjf Skellington said the following on 08/17/2009 06:59 PM: > So, I just set the conf/web.xml to 240 minutes and reloaded. > > /docs and /manager are set to 240 but my two OpenBD apps are still at > 30 and I dont see a session time out in their WEB-INF/web.xml files. > So I tried to set in WEB-INF/web.xml and the app will not load. > > Strange, time to hunt through the logs :-p > > On Aug 17, 4:52 pm, Matthew Woodward <[email protected]> wrote: > >> 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. >> -- >> Matthew Woodward >> [email protected]http://www.mattwoodward.com/blog >> >> Please do not send me proprietary file formats such as Word, PowerPoint, >> etc. as attachments.http://www.gnu.org/philosophy/no-word-attachments.html >> >> smime.p7s >> 4KViewDownload >> > > > --~--~---------~--~----~------------~-------~--~----~ 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 !! -~----------~----~----~----~------~----~------~--~---
