7.8.1 Explicit release reserving of the Explicit memory block when the automatic release functionality is disabled
The functionality of releasing the Explicit memory block is executed by dividing into two steps of reserving for release and the actual release process. You can perform an effective processing by respectively reserving multiple Explicit memory blocks and executing the release process together.
- Organization of this subsection
(1) Execution timing
In an application, if you place any object in the Explicit Heap, you can reserve release of the Explicit memory block by invoking one of the following Explicit Memory Management functionality APIs.
-
ExplicitMemory.reclaim(ExplicitMemory... areas)
-
ExplicitMemory.reclaim(ExplicitMemory area)
-
ExplicitMemory.reclaim(ExplicitMemory area0,ExplicitMemory area1)
-
ExplicitMemory.reclaim(Iterable<ExplicitMemory> areas)
-
BasicExplicitMemory.finalize()
Web container reserves the release of the objects placed by the J2EE server. For details on the execution timing, see 7.4 When using J2EE server objects placed in Explicit heap.
(2) Executed details
When you invoke an API described in (1), the Explicit memory block area that you specified in the argument of the API is reserved for release.
If you are using the API in an incorrect way, an API level exception might occur. For details, see 10.7 Exception class in the uCosminexus Application Server API Reference Guide.