Kbase P42348: CTRL-C and CTRL-BREAK causes character client session (connected in shared memory) to hang or produc
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/14/2005 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.1D
WebSpeed 3.1D
Windows NT 32 Intel/Windows 2000
SYMPTOM(s):
CTRL-C or CTRL-BREAK doesn't work with the Win32 character client during a lock conflict
When a lock conflict is experienced, the client sessions will hang indefinitely as CTRL-BREAK doesn't work with Win32 character client
Getting error 121 when a CTRL-C or CTRL-BREAK is performed
Wait or press CTRL-BREAK to stop. (121)
Win32 character client is connected through shared-memory.
CAUSE:
Bug# 20030131-011
CAUSE:
Expected console input to address lock conflict. Now we will handle console or signal input to resolve the conflict.
FIX:
1. Upgrade to 9.1D09/ 3.1D09 Service Pack
Or
2. Connect the Win32 character client via client/server mode to the database.
If all components are on the same machine, configure Broker to handle local loopback type of connections from clients running on the same physical machine.
a. Configure server as a Broker to handle remote client connections.
This can be done by starting the database broker with -H hostname and -S service name or port #.
b. Have clients sessions connect to the database with the same -H hostname and -S service name or port # that the broker was started with.