would get error reports here and there because of deleted variables and
other wackyness. It took a while to track down and even longer to solve them
all, but we did it.
It took some creative locking skills to get the sequence just right on part
of it, and some creative error reporting skills to keep the unfixable and
transparent (to users) errors from being reported on the rest.
We put an exclusive named lock around deleting variables, and a readonly
lock around large chunks of code that would throw these errors. It was
annoying because we could set a variable, then 5 lines later it would be
gone, so these whole chunks had readonly locks.
As for the unfixable errors I mentioned, it's things like, when a page takes
a while to load, a user will click logout before it loads, so sometimes they
can be 2-3 clicks down the road by the time that slow-loading page finishes,
and at the end, it includes a template that calls a session variable and
throws an error. Of course the user is 4 clicks beyond that, so they never
know it happens. These errors we trap on our error catching template and
refuse to report.
Test this stuff and see if that happens to you, then put your locking skills
to the test.
-nathan strutz
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 4:46 AM
To: CF-Talk
Subject: Single-threaded server probs
> Hi all,
>
> The server in question is implemented with Single Threaded Sessions
> (that's just the way it is :-)
>
> The problem with single threaded sessions (as I am sure you are aware)
> is that if a request is taking a little bit longer than usual, the
> user often tries clicking away from the screen, which of course just
> lines up another request against their session ID. This then
> generally brings the server down if the user is very click/trigger
> happy (guess we all want to be cowboys) as the requests just pile up
> and then... crash...
>
> Anybody got any (useful) insights on how to prevent this crash from
> happening with respect to the situations above? Any checking I can
> do.... it would be impossible to go back and retrofit apps (resource
> issues) so looking for a possible way to solve this generically.
>
> There are quite a few apps on the server and locking is not used much
> anywhere (again that's just the way it is, please don't moan to me
> about it unless it is def part of the solution)
>
> Comments would be appreciated.
>
> Thanks.
>
> --
> -dc [ cf5, ora8.1.7, iis5 ]
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
