Resolution:
Description:
=========
On some Unix platforms, the EMS server utilizes high virtual memory after the server  starts up when using a database store.

Environments:
==========
UNIX platforms

Resolution:
========

Based on our tests on different UNIX, Linux and Windows platforms, this high virtual memory issue should be an OS/JVM issue.

We used jconsole to remotly connect to two embedded JVMs running within two different EMS instances on two different machines (HPUX ita64). It showed that the "committed virtual memory" was -1, which is no limit, so that the SIZE (virtual memory size) in the UNIX top command of the EMS process showed the maximum available memory size on the machine. These two different machines had different free memory sizes, so that the SIZE (virtual memory size) showed different values.

However, this doesn't happen when the EMS instance was running on a Linux, AIX, Solaris or Windows box from our tests.  They all showed correct Virtual memory sizes for the EMS process when using embedded JVM. The “Committed Virtual memory” showed the correct size in JConsole.  

For example, for the EMS server on a Linux box, the "committed virtual memory" showed the value around  1.4 GB from jconsole, which is the virtual memory size of the EMS server process size.

From our tests, only HPUX ita 64 had such an issue (Commited Virtual memory shows -1, unlimited). We have not tested on all platforms but the available test results show that this is a Java/OS platform issue rather than an EMS issue.