Kbase P25029: AppServer processes remains in the LOCKED status, doing nothing.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
SYMPTOM(s):
AppServer processes remains in the LOCKED status, doing nothing.
The error happens when a program is executed, it always happens at the same spot.
After 30 minutes, the AppServer resumes processing, or goes back to AVAILABLE.
Using ADM2 code.
AppServer running in Stateless mode.
CAUSE:
This behavior is usually caused by record locks held by a persistent procedure on the AppServer.
If a persistent procedure acquires a lock serving one client request and, because of record scoping, does not release it at the end of the client request, the lock will not be released by a Stateless AppServer; instead it will persist until the persistent procedure releases it (be it implicitly or explicitly) or the AppServer process terminates (for example by trimming the AppServer servers down).
For this reason, following AppServer requests can be stuck on the lock held by the first AppServer process. After 30 minutes (or the number of seconds specified by the -lkwtmo startup parameter), the Lock Time Out will expire, and processing on the AppServer will resume.
FIX:
Investigate which locked record the LOCKED AppServer get stuck into, and then investigate your persistent procedures to see why one of them is not releasing it.