Note that on its Forums, CT today says that this is a problem that they are investigating and that, unlike the known issue with CFMX 6.1 and J2EE (the one addressed in their Knowledge Base article), this is something different because it happens even when the J2EE and CFMX sessions are nominally the same or the CFMX session is shorter than the J2EE session.
So it really does seem to be a new issue, and I expect we will hear something soon. Cheers, James Edmunds On Mon, 14 Feb 2005 06:15:29 -0400, Will Tomlinson <[EMAIL PROTECTED]> wrote: > Here's what CT replied with. It doesn't make sense, if I hadn't set > sessiontimeout in app.cfm. Wouldn't it've defaulted to 30? > > Thanks, > Will > > Will, > > This is not the case. I have checked in the web.xml file on your web server, > and the timeout is indeed set to 30. > > Please contact us again if you have any further questions. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:194886 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
