The Explicit Memory Management functionality inhibits the occurrence of a full garbage collection by using an area other than the Java heap (Explicit heap) as the Java object placement destination.

The following table describes the organization of this chapter.

Table 8-1 Organization of this chapter (Inhibiting full garbage collection by using the Explicit Memory Management functionality)

Category	Title	Reference location
Explanation	Overview of the Explicit Memory Management functionality	8.2
	Overview of the memory space used in the Explicit Memory Management functionality	8.3
	Objects placed in the Explicit heap when using a J2EE server	8.4
	Objects that you can optionally place in the Explicit heap in the application	8.5
	The life cycle of the Explicit memory block and executed processes	8.6
	Releasing the Explicit memory block when the automatic release functionality is enabled	8.7
	Releasing the Explicit memory block when the automatic release functionality is disabled	8.8
	Releasing the Explicit memory block by using the javagc command.	8.9
	Reducing the time required for automatic release processing of the Explicit memory blocks	8.10
	Reducing the memory usage of the Explicit heap that is used in an HTTP session	8.11
Implementation	Implementing a Java program that uses the Explicit Memory Management functionality API	8.12
Settings	Settings in the execution environment	8.13
Notes	Points to be considered when using the Explicit Memory Management functionality	8.14

#: There is no specific explanation of Operation and Precautions for this functionality.

For details on the mechanism of garbage collection, see 7. Memory Tuning of JavaVM in the uCosminexus Application Server System Design Guide.