Kbase P100360: How to handle locked record in a persistent object ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/01/2005 |
|
Status: Unverified
GOAL:
How to handle locked record in a persistent object ?
GOAL:
Why the persistent procedure is still in the Persistent Object list on the agent in Web Tools ( Workshop ) ?
FACT(s) (Environment):
WebSpeed 3.x
OpenEdge 10.x
FIX:
When using EXCLUSIVE-LOCK without NO-WAIT NO-ERROR the agent stops the request if a record is already locked by another user.
And this does not depend on how the transaction scoping is or whether the code runs in a persistent or a non-persistent procedure.
The agent ends the request after the lock timeout expires no matter what.
Because the request is stopped, abnormally in this case, the agent doesn't get to the point to run DELETE PROCEDURE and since the procedure is already allocated at the SESSION level it stays there.