In EAServer, the thread stack size property determines the amount of memory reserved for the call stack associated with each thread. The stack size must be sufficient to allow for nested intercomponent calls. However, if the stack size is too large, memory is wasted.
The default stack size is 256K on UNIX and on 32-bit Windows operating systems. This is appropriate for almost all situations, and provides adequate reserve memory for the largest case loads that have been tested by Sybase engineering and customers.
For production servers that see heavy use from large numbers of clients, you may want to decrease the stack size from the default value. Doing so can make the per-thread stack memory available for other uses. However, you must first run load tests on a test server to ensure that the stack size is adequate for the components running on the server. If the stack size is too small, client requests may fail with thread stack overflow errors, which are recorded in the server log.
Sybase recommends that you do not reduce the stack size if you run:
Components that call third-party DLLs or shared libraries
Java components that call native classes (including JDBC drivers that call out to native libraries)
For information on setting the stack size, see “Configuring server stack size” in the EAServer System Administration Guide.
You can also configure the stack size for Java threads, as described in “JVM memory allocation parameters”.
