Memory settings for the application server process

The application server process in which the system is deployed must be configured with the right amount of memory setting, or else the process runs out of memory when the system is running.

A single process running the system can support up to 50 user loads with optimal performance. Scheduled cron jobs and integration activities within a process also consumes additional memory. A higher user load on a single process also can result in memory errors and can potentially cause the process to terminate.

The following recommended memory settings are for a single process that is running the system with a small amount of capacity for reporting, cron tasks, and integration activity. The same settings also apply to the application server processes that are set up to process the integration load or the cron tasks as part of a clustered configuration. An application server process can run into a memory situation because of a large user load, large integration messages being processed, cron tasks that run for a long time and require more memory, bugs in the application code or the application server, and so on. When a memory situation occurs, identify the root cause. If the problem occurs because of a higher user load, adding additional servers helps.

WebLogic Server

If WebLogic Server is set up to run with JVM, use the following memory settings:

WebSphere Application Server

If you are using a WebSphere® Application Server, use the following memory settings for a 32 BIT JVM:

If you are using a WebSphere Application Server, use the following memory settings for a 64 BIT JVM:



Feedback