Kbase P53634: Error 3765 when using PSTIMER OCX & SESSION:TIME-SOURCE
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.x
SYMPTOM(s):
Application runs entirely on Citrix
Application sets SESSION:TIME-SOURCE to the database
Database is connected via client/server
All record locks are coded as EXCLUSIVE-LOCK
The NO-WAIT and NO-ERROR phrases are never used when a record is fetched with an EXCLUSIVE-LOCK
The PSTIMER OCX is used on every window to update the date and time
The OCX.Tick event for the PSTIMER OCX makes calls to the TODAY and TIME functions
Message recvd while waiting: uc_wait=, msg= (3765)
Message recvd while waiting: uc_wait=1, msg=50 (3765)
Message recvd while waiting: uc_wait=1, msg=67 (3765)
CAUSE:
Bug# 20031007-010
CAUSE:
The combination of using SESSION:TIME-SOURCE, PSTIMER OCX and EXCLUSIVE-LOCK record fetches without the NO-WAIT & NO-ERROR phrases caused an internal problem where the flag that is checked to determine whether asynchronous external ActiveX events should be thrown away became corrupt. This allowed these events to be processed when they should not have been. Since the OCX.Tick event called the TODAY and TIME functions and SESSION:TIME-SOURCE was set to the database calls to the database server were made each time those functions were invoked and periodically the database server was not in a state where it could properly handle those requests and consequently the 3765 error was received and the client process would either crash or hang.
FIX:
Upgrade to Progress 9.1D08 or later