> -----Original Message----- > From: James Smith [mailto:[EMAIL PROTECTED] > Sent: Friday, June 15, 2007 5:24 AM > To: CF-Community > Subject: Plea for help > > Does anyone know what would cause a user to switch sessions (or any > other > reason a basket would empty)?
Not to get personal, but you did ask. ;^) What's your architecture? Anything there worth examining? Specifically: +) Are you clustered? If so how is balancing in the cluster handled? Are clustered sessions enabled? If balanced with an appliance are "sticky sessions" (however defined by the appliance) handled? +)Any "odd" hardware between the app and the user? For example an SSL accelerator appliance? In general what are we talking about? Just an overview: server/hardware/versions/etc. Silly stuff you've almost definitely done but bear repeating: +) Check drive space. Stupid, yes - but something that's bit people in the ass again and again. Make sure you have lots of free space (or at least that you don't have very little). The most common culprits are old log files and temp files. +) Check your server/OS logs: is your application actually up as much as you think it is? There are plenty of situations in which your app/server/OS may reset itself quickly/automatically - you might not notice in the course of world events but it would kill your sessions. +) Increase logging. Turn on system monitors (perfmon) and up logging states wherever possible. +) Add some logging to the app - log when items are added the cart by IP/time/etc. Something that will hopefully narrow things down. Some other ideas: +) Use that anger! Don your flame-suit and get on those public forums. Ask for specifics (get time of incident, browser, OS, etc - see if they can replicate the problem or if it were point in time). Better yet if you can get approval offer a small reward (a small gift certificate or something) for helping out - nothing eliminates momentary inconvenience like cold, hard cash. +) In the same vein consider a parallel task of improving your error reporting. Two aspects here. Improve your online error reporting (if you haven't already) to include browser details, clickstream (if you have it) and so forth. (I've been collecting clickstream data for years now and find it invaluable for tracing down odd bugs). Secondly make sure that your support personnel are asking the right questions: browsers/versions/OS/time/etc - nothing is more frustrating than trying to deal with a poorly taken problem description/history. Jim Davis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 & Flex 2 Free Trial http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJU Archive: http://www.houseoffusion.com/groups/CF-Community/message.cfm/messageid:236712 Subscription: http://www.houseoffusion.com/groups/CF-Community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.5
