Kbase P132672: A client running on Kermit95 causes the database to shut down when its session terminates abnormally
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/26/2009 |
|
Status: Unverified
SYMPTOM(s):
The database shuts down when a client dies holding a shared memory lock.
A "user died holding shared memory lock" error is written to the database log file.
User <num> died holding <num> shared memory locks. (2522)
FACT(s) (Environment):
Clients are connected to the database using Kermit95.
Kermit95 is a communications/terminal emulation package developed at Columbia University.
Kermit95 sends a hangup signal after choosing the "Hangup" option from the pull-down menu .
Kermit95 sends a hangup signal after 'X'ing or closing out the window.
Kermit95 does not send any signal when the Kermit95 session is killed.
There are no options in Kermit95 to set signals for specific actions.
Windows
OpenEdge 10.0B
OpenEdge Category: Administrative
CAUSE:
This is expected behavior. Kermit95 does not send any signal when a Kermit95 session is killed or terminated abnormally. If the client is holding a shared memory latch or a buffer lock when it terminates abnormally, the database will shutdown when the broker or watchdog process detects that the client terminated while holding the latch or buffer lock.
FIX:
Switch to connecting the Kermit95 clients as local loopback clients utilizing the -S <service> and -H <host> parameters. If the Kermit95 client terminates abnormally, the server it is connected to will cleanly disconnect the client since the server holds latches on behalf of the clients connected to it.