Salesforce

** stget: out of storage error during AppServer startup

« Go Back

Information

 
Title** stget: out of storage error during AppServer startup
URL Namestget-out-of-storage-error-during-AppServer-startup
Article Number000185064
EnvironmentProduct: OpenEdge
Version: 10.x, 11.x and later
OS: Windows 2008 and later
Question/Problem Description
** stget: out of storage error during AppServer startup

The error occurs when the broker spawn a large number of agents (+10) at startup.

The error is also likely to occur when those initial agents connect in shared memory to the OpenEdge database with a large number of database buffers (-B).
Steps to Reproduce
Clarifying Information
Windows paging file is disabled or is set to a fixed size.

The Windows Task Manager reports that 20-40% of the physical memory is available.
Error MessageAppServer agent log reads:

With no initial shared memory connection attempt to the database:
** stget: out of storage. (6498)

With an initial shared memory connection attempt to the database:
** stget: out of storage. (1450)
Unable to attach shared memory <shmname>, error <n>. (1720)


Windows event viewer reads:

Windows successfully diagnosed a low virtual memory condition.
Defect Number
Enhancement Number
Cause
The system is unable to reserve a contiguous segment of virtual address space for the process. 

When you start a 64-bit AppServer process, Windows can allocate up to  8GB of user-mode virtual memory address space to that process (2-3GB for 32-bit processes). 

The low virtual memory error occurs when the OS is unable to allocate a contiguous segment of virtual address space because the paging file size is set too low (or paging is disabled). 
Resolution
Re-enable paging and/or increase the pagefile size. You may let Windows manage the size of the paging file. Should you be facing disk space limitation, and require a non-floating the pagefile size,  Microsoft recommends a minimum size corresponding the the amount of physical memory. Therefore, in the unfortunate event of a system crash, the OS will be able to generate a complete memory dump.ear.

In the case where the error occurs while attaching a shared memory segment (1450)(1720), reducing the shared memory segment size (-shmsegsize) in the case of shared-memory connections to the database, will also help alleviating the issue, the larger the (-B) parameter value.
Workaround
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:22 AM

Powered by