Name: gm110360 Date: 09/04/2002


FULL PRODUCT VERSION :
java version "1.4.1-rc"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-rc-b18)
Java HotSpot(TM) Client VM (build 1.4.1-rc-b18, mixed mode)

FULL OPERATING SYSTEM VERSION :
doen't apply

A DESCRIPTION OF THE PROBLEM :
Under some circumstances it might be necessary, that a Java
server application needs more memory than it has been given
with the -Xmx parameter.

Reducing the max heap size might require objects to be
relocated in the heap. Increasing not.

Solution might be related to bug#4642192, if bug#4642192
solution requires relocation of objects in the heap.

It's "boring" to restart a Java application just to give it
more memory. This gets more important for server
applications. For example J2EE app servers that get more and
more applications...

EXPECTED VERSUS ACTUAL BEHAVIOR :
Methods like:

public void setMaxHeapSize(long heapSize);
public long getMaxHeapSize();



REPRODUCIBILITY :
This bug can be reproduced occasionally.

CUSTOMER WORKAROUND :
Restart the whole application.
(Review ID: 164039)
======================================================================