The request that runs this code must have also run a cfapplication tag and therefore kept the session alive, no?
On 12/10/05, Terry Ford <[EMAIL PROTECTED]> wrote: > This is what appears to be happening: > > The thread with this code switches out precisely after the structkeyexists() > evaluates true. The thread that clears inactive sessions becomes active > right after it has previously evaluated this session as expiring, so it > deletes the session. The original thread becomes active again, and now has > no session, so the second part of the CFIF "session.acceess eq 1" evaluates > as an error. > > If this is the case then I don't think the race condition could even be > prevented by CFLOCKing the CFIF block, as the session-clearing thread would > ignore it. It probably hardly ever comes up because the chance of someone > suddenly waking up and executing a template that interweaves in that fashion > at the exact millisecond that the session times out is rather small. Cute, > though. -- CFAJAX docs and other useful articles: http://jr-holmes.coldfusionjournal.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:226719 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
