The Web container secures and releases the Explicit memory block area. The objects for communication used for communication between a Web container and a redirector are usually reused as a permanent connection, and retained when the Web server is being started.

If the connection is disconnected or reconnected due to the occurrence of failure between the Web container and the redirector, the objects for communication are destroyed and regenerated. At that time, the destroyed objects for communication remain in the Tenured area.

To prevent this, on a J2EE server, place the objects for communication between a Web container and a redirector in the Explicit heap and thus prevent unnecessary objects from remaining in the Tenured area and inhibit a full garbage collection.

This subsection describes the flow of placing Explicit memory blocks corresponding to the timing of establishing and disconnecting communication.

When communication is established

When connection is established, one Explicit memory block is created for one connection. The objects for communication with the redirector are placed in the created Explicit memory block.

When communication is disconnected

When communication is disconnected, release of one Explicit memory block is reserved for each object, for communication with the redirector placed in the Explicit memory block.

The release is reserved immediately after communication is disconnected. The Explicit memory blocks reserved for release are actually released when the copy garbage collection or full garbage collection is executed after that. At that time, all the areas reserved for release, are released.