WebLogic Server Process Using All System Memory

Content

When running WebLogic Server the Windows Process (BEASVC.EXE and/or JAVA.EXE) continually uses System Memory and the memory is not released. The memory usage increases over time and transaction load. When monitoring the WebLogic Server there is no indication of any issue. The garbage collection is executing correctly and the system is managing the memory correctly.

Solution

There is an access log file that logs WebLogic Server file access. This file can grow quickly if there are a number of users connected. When WebLogic is stopped and restarted this file is not recreated, the existing file is appended to. With a larger file the Java Virtual Machine (JVM) is not working as efficiently as it should. To alleviate this issue the ACCESS.LOG file can be deleted whenever WebLogic is stopped/shutdown. The file will be recreated when WebLogic is started.

In WebLogic Server 6.1 the ACCESS.LOG file is located in bea\wlserver6.1\config\mydomain\log

In WebLogic Server 7.0 the ACCESS.LOG file is located in bea\user_projects\mydomain\maximoserver

In WebLogic Server 8.1 the ACCESS.LOG file is located in bea\user_projects\domains\mydomain\maximoserver

The access.log file can also be configured to rotate. From the WebLogic Admin Console select the Maximo Server Application Server. Click the Logging tab and then the HTTP tab. The rotation type field allows to rotate the file by size or time. Click apply. The Maximo Server will need to be stopped and started for the change to take affect.