The following table describes the events that might occur due to the memory size of the Explicit heap, how the Explicit Memory Management functionality is used, how the Java application is designed, and the execution environment settings.
Table 7-9 Events that occur during the application of the Explicit Memory Management functionality and the reference locations for the actions
No. | Event | Reference location for the action |
---|---|---|
1 | The Explicit heap is full and an attempt to generate an object in the Explicit memory block fails. | 7.13.3 |
2 | An attempt to generate an Explicit memory block fails. | 7.13.4 |
3 | Even if the Explicit Memory Management functionality is used, a full garbage collection occurs frequently. | 7.13.5 |
4 | The automatic release processing of the Explicit memory block takes a long time. | 7.13.6 |
You can check whether these events are occurring from the event log of the Explicit Memory Management functionality. For details on the verification methods, see 7.13.1 Investigating the usage (snapshot) of Explicit heap at a certain point, and 7.13.2 Investigating the transition of usage status. For details on the event log contents of the Explicit Memory Management functionality, see 5.11 Event log of the Explicit Memory Management functionality in the uCosminexus Application Server Maintenance and Migration Guide. Note that for ready visibility, \ has been entered at the linefeed locations in the examples of output described in this section. There is no linefeed in the actually output content.