Kbase P106588: The Progress/400 DataServer broker hangs and consumes all the CUP resources after abnormal disconnec
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/03/2010 |
|
Status: Unverified
SYMPTOM(s):
The Progress/400 DataServer broker hangs and consumes all the CUP resources after abnormal disconnection of a client.
The system needs to be IPL everytime the problem occurs
The following error was displayed in the JOBLOG:
Job name . . . . . . . . . . : PROSERVER User . . . . . . : GLAUR Number . . . . . . . : 507139
Job description . . . . . . : QDFTJOBD Library . . . . . : QGPL Section number . . . . . . . : 4214
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
MCH2605 Escape 40 DATE TIME < ckSpaceLoc 000E5C PROSERV PROGRESS *STMT
From Program . . . . . . . : RmslUnlockSpaceLoc To module . . . . . . . . . : AS4LOCK2 To procedure . . . . . . . : syswake
Statement . . . . . . . . . : 22 *PRCLT Message . . . . : Invalid space location unlock request
Cause . . . . . : You tried to unlock a space location lock that is not held by the requesting thread.
Uses Progress/400 lock table for the share-lock used in the application
After changing the program logic to not use share-lock, therefore lock table, the problem was cured.
FACT(s) (Environment):
Progress 9.1C
Progress/400 DataServer
CHANGE:
Upgraded from Progress/400 V8 to 9.1C07
CAUSE:
The exact cause is unknown at the time of this writing
FIX:
The workaround is to delete Progress/400 the lock table and not use it.