Kbase P147824: Error (1720) when AppServer tries to connect to shared memory
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/08/2009 |
|
Status: Unverified
SYMPTOM(s):
Unable to attach shared memory <shmname>, error <n>. (1720)
Error (1720) when AppServer tries to connect to shared memory
<procedure name> <procedure type> procedure ended with an QUIT condition. (8027)
Connection failure for host <host_name> port <port> transport <transport_name>. (9407)
State-reset server disconnecting non-command-line database <name>. (7982)
Disconnecting from database <database>, user number <usernum>. (9545)
User-defined function '<function>' invoked dynamically but could not be found. (5639)
FACT(s) (Environment):
Windows Server 2003 Enterprise
OpenEdge 10.1B03 Service Pack
CAUSE:
The Windows API function openfilemapping() fails because not enough contigious Memory is available for the Virtual Memory Manager to provide. That means that ultimately this is a system resource issue, not a Progress issue.
FIX:
There are two possible ways to alleviate the issue without any major architectural changes (e.g. migrate to a 64-Bit Linux system): 1. Rather than use connect/disconnect procedures to establish the database connection when the clients connect to the STATE-RESET AppServers, establish the DB connection immediately when the AppServer itself is started. This would reduce the amount of fragmentation caused by the frequent connects/disconnects. 2. Reduce the number of STATE-RESET AppServers that connect to the Shared Memory via self-service and have them connect to the DB via client networking (remote servers) instead.