on 11-25-2008 8:10 AM
Hello all,
I am not fully aware if this is the right thread to post this, but I have been looking for additional tips in tuning our Developer Workplace (J2EE Engine). After a few deploys (3-5) deploys, the server node restarts -- possibly a shortage in memory and/or the GC function fails to aid in the invalidation of the then used resources.
Running on 2GB RAM, by the way.
Dispatcher Settings:
Max Heap Size : 32
-Djava.security.policy=./java.policy
-Djava.security.egd=file:/dev/urandom
-Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-Xms15m
-XX:NewSize=5m
-XX:MaxNewSize=5m
-XX:NewRatio=3
-XX:+DisableExplicitGC
-verbose:gc
-XX:+UseConcMarkSweepGC
Server Settings
Max Heap Size : 512
-Djava.security.policy=./java.policy
-Djava.security.egd=file:/dev/urandom
-Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-Djco.jarm=1
-XX:MaxPermSize=128M
-XX:PermSize=64M
-Xms50M
-XX:NewSize=15M
-XX:MaxNewSize=15M
-XX:+DisableExplicitGC
-verbose:gc
-Xloggc:GC.log
-XX:+PrintGCDetails
-XX:+PrintGCTimeStamps
-Djava.awt.headless=true
-Dsun.io.useCanonCaches=false
-XX:SoftRefLRUPolicyMSPerMB=1
-XX:SurvivorRatio=2
-XX:TargetSurvivorRatio=90
-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
Also, I have shut down optional services via the Visual Administrator.
Any help?
Thank you in advance.
Hi,
Even you can use Template Configuration Tool to tune the Web AS Java depending up on the scenario used.
For more information on Template configuration Tool see the link below
http://help.sap.com/saphelp_nw04/helpdata/en/12/fb8540ae1dbb4de10000000a1550b0/frameset.htm
Rgds
Radhakrishna D S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jan,
Yes, it might be due to be memory bottleneck which is caused by the incorrect memory parameters. To recoomend you the correct paramters, its required to know your available memory, Processor type (32 bit / 64 bit / windows/ unix) .
The following note will help you to set the correct values.
Note 723909 - Java VM settings for J2EE7.0
Hope this helps.
Regards,
Jazz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jan Michael Jaudian,
Please check out the below link :
You will find a lot like this in SDN as well as help.sap.com Just ask the both....
Regards,
S.Manu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.