Search: Advanced search
Please enter a keyword or ID
Surround SCM Server Does Not Start Due to Memory Issues
The Surround SCM Server does not start and the server log contains memory errors or unhandled exceptions.
The Surround SCM Server computer does not have enough memory to cache branches during server start up.
Mainline branches are always cached when the Surround SCM Server starts. By default, baseline, snapshot, and workspace branches are set to cache on demand, which means they are cached when users perform actions that access a branch.
When the Surround SCM Server starts, the most recently used cache on demand, or dynamic, branches as of the last server shutdown are cached. If these branch types are changed to always cache, they are always loaded when the server starts. As additional branches are created, the cache may become too large and cause memory issues and slow server startup times.
Note: You may also want to adjust the caching server options to reduce the number of cached dynamic branches and set other options. See the help for information about caching server options.