8. Inhibiting Full Garbage Collection by Using Explicit Memory Management

With Application Server, you can use a memory space other than the Java heap as the Java object placement destination when executing a Java application. The function is called the Explicit Memory Management functionality. You can inhibit the occurrence of a full garbage collection by effectively using the Explicit Memory Management functionality.

This chapter describes how to inhibit a full garbage collection by using the Explicit Memory Management functionality.

Note that you cannot use the Explicit Memory Management functionality if the -XX:+UseParNewGC option is specified as a type of the copy garbage collection.

Organization of this chapter

8.1 Organization of this chapter

8.2 Overview of the Explicit Memory Management functionality

8.3 Overview of memory space used in the Explicit Memory Management functionality

8.4 When using J2EE server objects placed in Explicit heap

8.5 Objects that you can optionally place in the Explicit heap in the application

8.6 Life cycle of Explicit memory block and executed processes

8.7 Releasing Explicit memory blocks when the automatic release functionality is enabled

8.8 Releasing Explicit memory blocks when the automatic release functionality is disabled

8.9 Releasing Explicit memory blocks by using the javagc command

8.10 Reducing time required for automatic release processing of Explicit memory blocks

8.11 Reducing memory usage of the Explicit heap that is used in an HTTP session

8.12 Implementing the Java program that uses the Explicit Memory Management functionality API

8.13 Settings in the execution environment

8.14 Precautions for using the Explicit Memory Management functionality