984089 wrote:Those are boundaries only, configuration.
we have two parameters Minimum heap size (-Xms2G) and maximum heap size(-Xmx2G).I just wanted to know that 2% is for the minimum heap size or the maximum heap size that was configured as JVM parameters.Can you please make it clear if my understanding is not correct..
But I could not get from you what is the "actual heap size".The heap as it exists when the JVM is actually running, which is minimally what you provided with Xms and maximally what you provided with Xmx. So lets say you set the minimum at 100mb and the maximum at 200mb, the heap size will start at 100mb in size. When you create 150mb worth of objects, the heap will be 150mb (give or take). If you claim 50mb worth of objects more, the heap will be 200mb. If you try to use more memory, you'll get an out of memory error because the heap is not allowed to grow beyond 200mb.
984089 wrote:I have been using Java since 1.2 and I've upgraded to every version available. Besides setting proper heap space and debug settings I have -never- had to specifically configure anything.
Is there anything specific to jre 1.6 that we missed to configure here which might caused this error ?.I am giving my JVM parameters once again..
SD13 wrote:Did you update ANYTHING else? Like third party libraries, like JEE containers, like JDBC drivers, like OS/Platform?
My concern over here is our application is running in jre 1.4 for years, we haven't faced this OutOfmemoryError .Its only a couple of days since we moved to 1.6 ,we started facing this issue