> The problem with that is that I would be calculated the > "expected" timeout, and not the actual value that Coldfusion > is using. In theory they should be exactly the same, but in > practice I am trying to track down a problem where Coldfusion > is expiring sessions much earlier than it should.
This wasnt really the intended purpose of my proposal. What OS and CF version are you using? There were some memory leaks inherent with cfmx on linux in the past which would have caused premature session expiry. > If I could "walk" the list of active sessions, then I could > see if the problem is happening to ONE session at a time, or > to ALL sessions across the server. > Just calculating the "age" value of each session will not > help me to see why CF is expiring early. > -Peter There is a custom tag available called cf_sessionWatch http://www.cfdev.com/products which may be of some use to you. HTH, Dave ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. http://www.cfhosting.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
