Problem: Unable to establish additional ArcSDE connection once XX connections are reached
Users may need to make many connections to the ArcSDE server, but once a certain number of connections are established, no new connections can be made.
The giomgr process may appear to be hung and not accepting new connections while existing gsrvr processes continue to operate.
This article addresses two possible causes of this problem.
The CONNECTIONS parameter in the giomgr.defs file restricts the number of concurrent connections allowed, so it needs to be increased.
On Windows machines, the ArcSDE service is started as a non-interactive desktop. The maximum amount of heap memory allocated to non-interactive desktops is limited by a Windows initialization parameter called SharedSection. The desktop heap in the WIN32 subsystem may be depleted, causing the connections to fail.
Solution or Workaround
To resolve the first cause, increase the maximum number of connections to ArcSDE, navigate to the %SDEHOME%/etc folder on the server, and edit the giomgr.defs file. Below is a workaround to solve this problem:
Navigate to %SDEHOME%\etc, and open the giomgr.defs file.
Scroll down to the section that appears similar to:
# If more server connections are needed,
# increase this value for CONNECTIONS parameter.
CONNECTIONS 48 # maximum number of connections
# NOTE: On windows machines, you may need to
# increase server non-interactive desktop memory.
Increase the CONNECTIONS parameter by commenting out the original parameter, and set it to the required value.
Save changes to the giomgr.defs file, and import the new settings into the server_config table by opening a command prompt and typing:
sdeconfig -o import -f %SDEHOME%\etc\giomgr.defs -i <sde service name> -D <sde database> -p <sde password> -u <sde user name>
To resolve the second cause, increase the memory allocated to the heap.
The instruction below includes making changes to essential parts of your operating system. It is recommended that you backup your operating system and files, including the registry, before proceeding. Consult with a qualified computer systems professional, if necessary.
Esri cannot guarantee results from incorrect modifications while following these instructions; therefore, use caution and proceed at your own risk.