Hi Olaf,
> has anybody informationen about the memory management
> of the WEB As 6.20 or the JVM?
There is an article here on SDN that includes such stuff:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how to tune sap j2ee engine 6.20.pdf
> How can I see when a garbage collection takes place?
NOT.
> How much memory should be allocated by the server
> nodes?
See the article. Anyway, this is depending on a lot of factors.
Regards,
Benny
Hi Olaf,
Server nodes are bound by the maximum heap size (-Xmx) value you specify with JVM parameters. Based on the end users activities and the applications you deployed within the WAS, Java process will allocate memory. To find out how much memory is allocated and recycled, you can get some info when you add -verbose:gc with as JVM options. If you see very frequent and long GC (more than few seconds, depends on the "mx" value and other values NewSize, etc.) you need to increase your "mx" value in case you have memory available in the box.
In summary, to have some idea what is going on within the JVM as far as memory is concerned, you can get it from -verbose:gc output.
Thanks,
Swapan
Hi, Olaf.
If you are using JDK 1.4.2.XX, you can see the GC trace with the following settings.
-verbose:gc
-XX:+PrintGCTimeStamps
-Xloggc:<output file for GC trace>
If you want to see more detailed GC trace, add the
-XX:+PrintGCDetail
option also.
If you want to visualize the above output, you can try GCViewer from here.
http://www.tagtraum.com/gcviewer.html
The GCViewer is very simple and easy to use but one problem is that GCViewer cannot parse PrintGCDetail option(That's why i referred to this option separately).
Thanks.
Add a comment