Kbase 16904: Roundtable client process crashes and disconnects
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Roundtable client process crashes and disconnects
DRAFT COPY - Currently under review and edit.
Advice for customers whose roundtable client process has died or
disconnected badly (due to power outage for instance). After a reboot
and using RTB again, users reconnect to the RTB database, try to use
the module they were editing during the disconnect, and get errors.
The error when trying to edit the module is: "unable to lock this
object for editing". When the user tries to unlock the object he gets
the error: "no rountable lock exists for the modulename." What
is happening is that the Progress RTB server obtained a lock on a
record for the module they were editing before the crash. After the
crash the client process went away, but the server never cleaned up
after it, and it still is holding the lock for that process. After
rebooting the client, the reconnection to the server is a different
process altogether. This new client then tries to edit the same
module and the server blocks the edit since it can't obtain a lock.
The client gets the errors noted above.
What the user can do: From the database server shutdown, kill their
'phantom client' and the lock on the object record will go away. An
alternate would be to stop and start the RTB server.
Progress Software Technical Support Note # 16904