At 02:31 PM 5/18/2001 -0400, Robert F. Tulloch wrote:

>But, it all it did was say update one field in the
>"cumulative" record or whatever it is, that could be done same way in sp
>called in
>wait loop and lock on table with common record. The table is locked, sp
>called,
>commited/unlock and the next one goes. Why would it bring to "grinding halt"?

I believe the problem showed up at about 50 users. Rather than waiting
quietly for the "cumulative" record to be free, they'd get an error and
retry immediately. Eventually, the volume of retries overwhelmed the
server, leading to more retries, etc. I believe it's called "live lock".



Regards,

Ann