D
dbeavon
Guest
Can you confirm whether webspeed applications have to deal with the STOP conditions that occur because of lock-wait timeouts? I don't have experience with webspeed, but the docs do appear to say that webspeed has a different default lock-wait timeout than other types of ABL clients (10 sec vs 30 mins). I just found another thread that talks about the possibility of changing lock-wait-timeouts errors and making them CATCH'able. community.progress.com/.../27280 Hopefully we'll see some changes in this area. It seems pretty disruptive for the whole ABL session to crash, simply because a record isn't available. I guess at some point it must have been unthinkable for two people to be trying to use the record at once. Either that or Progress wanted everyone to use NO-WAIT whenever locking records.
Continue reading...
Continue reading...