On 7/13/06, Casey C Cook <[EMAIL PROTECTED]> wrote: > For the past 4 months we have been experiencing dozens of "invalid > session" errors per day. (and just recently reported by users!!!??!!) Ive > been doing some reading and one solution was setting a web.xml setting to > number equal to some timeout, however, I was told our "server setup" does > not use a web.xml file. Other people have posted coding solutions, but > outfitting dozens of applications with a piece of code to account for this > issue really isnt an option being considered at this point. Some of the > posts I was reading are 5 months old of people reporting the same issue, > my questions are: 1) Has a hotfix or other permanent solution been found > to this problem? 2) What is the definitive cause of this issue? > > Environment stuff: > We are currently running CF Version: 6,1,0,63958 > Windows and unix environments > Currently J2EE session variables is checked / are being used > The error suddenly appeared in the logs on Feb 22nd of 2006 and not a day > has gone by without the error since. > > Sample error from the application log: > "Error","jrpp-145","07/13/06","08:22:56","myapp","Session is invalid The > specific sequence of files included or processed is: > E:\inetpub\myapp\index.cfm " >
First off, your current MX install version is out of date. The latest version of ColdFusion MX 6.1 is 6,1,0,83762, so I'd highly recommend getting that installed first to take care of lots of bug fixes (plus any subsequent hotfixes released located here:http://www.adobe.com/go/b3a939ce). Second, the response you got was just plain wrong. There is definitely a web.xml file. The ColdFusion MX engine is just a series of J2EE servlets that *must* be defined in a web.xml file, so it has to be there. For the record, it's located in your WEB-INF directory root. I've only ever used the Enterprise version of CF, but my understanding is that the standalone version follows the same path structure. In that file is where you need to set this if it's not defined: <session-config> <session-timeout>XXX</session-timeout> </session-config> Note that the XXX time above is in minutes and you should set this to be greater than the CF Administrator timeout for session variables (the max timeout value, not the default timeout value). Incidentally, I think the CF Updater that you're missing is the one that actually fixes this bug. But hold on to the above instructions just in case. Hope this helps. Regards, Dave. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/cf_lists/message.cfm/forumid:4/messageid:246468 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
