Kbase P34044: Procontrol may fail to allow a client process spawned from O
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
28/07/2003 |
|
Status: Unverified
FACT(s) (Environment):
Windows
FACT(s) (Environment):
Progress 8.x
FACT(s) (Environment):
Progress 9.x
SYMPTOM(s):
Procontrol may fail to allow a client process spawned from Other Tasks to re-connect to a database with large values for -B with an 8k blocksize database
Database started with -B 180000 and blocksize of 8K
Unable to attach shared memory <shmname>, errno <n>. (1720)
CAUSE:
Bug 20030708-004
CAUSE:
Scenario:
Client is spawned as an Other Task from ProControl.
Database A has 8K blocksize and -B 180000
The code that the client runs causes it to connect to database A; disconnect from database A; connect to database B; disconnect from database B; then connect to database A again.
At the point where it tries to re-connect to database A the process reports Progress error 1720.
Problem only exhibits when client is spawned from Other Tasks of ProControl.
This limitation seems to be caused by an internal limitation within ProControl.
ProControl has been retired and since there are work-arounds to this problem the this will not be fixed.
FIX:
Several workarounds exist:
1) Use a 3rd-party scheduler package to launch the program.
(e.g. Norton Scheduler or WinAT are examples of scheduling packages)
2) Use an Icon with the same startup parameters as those used within Procontrol
3) Use a batch script
4) Manually give the commands from a command line