on 07-24-2014 9:15 AM
Go to F:\usr\sap\SLM\DVEBMGS00\j2ee\configtool and open the configtool.bat file and set 2048M for Max Heap Size for the server node.
Restart the system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Invalid maximum heap size: -Xmx0M
I still see that error message.
Do not mention -Xmx anywhere in the configtool parameter section.
The Max Heap Size field is for -Xmx
If you have changed the Max Heap Size field to 2048M then save it by using the save button available at the top of the configtool.
Provide the screen shot of your configtool.
RB
RB,
I have removed XSS2M and restarted the J2ee but still same error occurs.
Log:
[Thr 6084] JLaunchISetDebugMode: set debug mode [no]
[Thr 6592] JLaunchIStartFunc: Thread 6592 started as Java VM thread.
**********************************************************************
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 2097152 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -XX:MaxNewSize=341M
-> arg[ 4]: -XX:NewSize=341M
-> arg[ 5]: -XX:MaxPermSize=1296M
-> arg[ 6]: -XX:PermSize=512M
-> arg[ 7]: -XX:SurvivorRatio=2
-> arg[ 8]: -XX:TargetSurvivorRatio=90
-> arg[ 9]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 10]: -XX:+HandlePromotionFailure
-> arg[ 11]: -XX:+UseParNewGC
-> arg[ 12]: -XX:+DisableExplicitGC
-> arg[ 13]: -XX:+UseTLAB
-> arg[ 14]: -XX:+PrintGCTimeStamps
-> arg[ 15]: -XX:+PrintGCDetails
-> arg[ 16]: -verbose:gc
-> arg[ 17]: -Dsun.io.useCanonCaches=false
-> arg[ 18]: -Djava.awt.headless=true
-> arg[ 19]: -Djco.jarm=1
-> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 22]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 23]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 24]: -Djava.security.policy=./java.policy
-> arg[ 25]: -Dsys.global.dir=F:\usr\sap\SLM\SYS\global
-> arg[ 26]: -Dapplication.home=F:\usr\sap\SLM\DVEBMGS00\exe
-> arg[ 27]: -Djava.class.path=F:\usr\sap\SLM\DVEBMGS00\exe\jstartup.jar;F:\usr\sap\SLM\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 28]: -Djava.library.path=C:\j2sdk1.4.2_13-x64\jre\bin\server;C:\j2sdk1.4.2_13-x64\jre\bin;C:\j2sdk1.4.2_13-x64\bin;F:\usr\sap\SLM\DVEBMGS00\j2ee\os_libs;C:\j2sdk1.4.2_13-x64\jre\bin\server;C:\j2sdk1.4.2_13-x64\jre\bin;E:\oracle\SLM\11203\bin;F:\usr\sap\SLM\DVEBMGS00\j2ee\os_libs;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\Dell\SysMgt\RAC5;C:\Program Files (x86)\Dell\SysMgt\oma\bin;C:\PROGRA~2\CA\SHARED~1\SCANEN~1;C:\PROGRA~2\emailrelay\;C:\Program Files (x86)\CA\BrightStor ARCserve Backup;\bin\OPatch;C:\Program Files (x86)\Windows Imaging\;C:\j2sdk1.4.2_13-x64\bin;C:\PROGRA~1\CA\SHARED~1\SCANEN~1;F:\usr\sap\SLM\DVEBMGS00\exe;F:\usr\sap\SLM\SYS\exe\uc\NTAMD64
-> arg[ 29]: -Dmemory.manager=0M
-> arg[ 30]: -Xmx0M
-> arg[ 31]: -Xms2048M
-> arg[ 32]: -DLoadBalanceRestricted=no
-> arg[ 33]: -Djstartup.mode=JCONTROL
-> arg[ 34]: -Djstartup.ownProcessId=5228
-> arg[ 35]: -Djstartup.ownHardwareId=Z1131074580
-> arg[ 36]: -Djstartup.whoami=server
-> arg[ 37]: -Djstartup.debuggable=no
-> arg[ 38]: -DSAPINFO=SLM_00_server
-> arg[ 39]: -DSAPSTART=1
-> arg[ 40]: -DCONNECT_PORT=3023
-> arg[ 41]: -DSAPSYSTEM=00
-> arg[ 42]: -DSAPSYSTEMNAME=SLM
-> arg[ 43]: -DSAPMYNAME=sap2apsrv1_SLM_00
-> arg[ 44]: -DSAPPROFILE=F:\usr\sap\SLM\SYS\profile\SLM_DVEBMGS00_sap2apsrv1
-> arg[ 45]: -DFRFC_FALLBACK=ON
-> arg[ 46]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 47]: -DSAPSTARTUP=1
-> arg[ 48]: -DSAPSYSTEM=00
-> arg[ 49]: -DSAPSYSTEMNAME=SLM
-> arg[ 50]: -DSAPMYNAME=sap2apsrv1_SLM_00
-> arg[ 51]: -DSAPDBHOST=sap2apsrv1
-> arg[ 52]: -Dj2ee.dbhost=sap2apsrv1
**********************************************************************
Invalid maximum heap size: -Xmx0M
[Thr 6592] *** ERROR => JHVM_LoadJavaVM: Cannot create Java VM (rc=-6) [jhvmxx.c 703]
[Thr 6592] *** ERROR => Cannot load Java VM (server) (rc=-1) [jlnchxxi.c 836]
[Thr 6592] **********************************************************************
[Thr 6592] *** ERROR => Java VM initialization failed.
[Thr 6592] *** Please see SAP Note 943602 , section 'Java VM initialization issues'
[Thr 6592] *** for additional information and trouble shooting.
[Thr 6592] **********************************************************************
[Thr 6592] JLaunchCloseProgram: good bye (exitcode = -1)
Regards,
Farkath C
Hi,
Open instance.profile in /usr/sap/SID/j2ee/cluster
Open and remove this parameter -xmx0M, replace it with -xmx2048M restart the system.
Now once your system comes up, goto configtool and remove xmx0M as you have already maintained maxheapsize in your screenshot. Also, you can add -xmx2048M, which would not make any sense ay it already there.
Divyanshu
Farkath,
The setting could be coming from any of several different areas that you can access with Config Tool. Start by looking under cluster-data... instance_IDxxxxxx. Select the instance node, and check first on the Message Server & Bootstrap tab to ensure there is no -xmx setting in the java parameters. Then look on the Servers General tab. Here you can set the Max heap size to 2048, and then check in the java parameters that there is no -xmx parameter. If you make any change, such as deleting the parameter, be sure to hit the 'Save' icon before moving on to another area.
After this, under the instance node, select your dispatcher node and check that the max heap size is set to something like 545 (or at least, not zero), and again that there is no -xmx parameter in the java parameters.
Now select the server node, and do the same thing. Max heap size should be equal to the setting from the instance node for servers general: 2048. Sometimes you might find a -Xmx parameter in the java parameters for this node, but if you do, either delete it or make sure the value is the same as what you set for max heap size (i.e., 2048).
Again, save after each change. When you have made all your changes, exit the config tool, and restart everything.
Regards,
Matt
In the first screenshot, for the instance node, you have a mismatch between the max heap size, set to 2048, and the java parameter -Xmx1024m. Delete the -Xmx1024m parameter.
However, beyond this, the settings looks correct, so I think you are having the problem that Reagan suggests, where your Config Tool is not updating your instance.properties file correctly. Follow his suggestions, make a backup copy of the file, then edit it in the manner recommended in the Note he linked (i.e., delete the parameter).
ID2849550.JavaParameters=-Xms2048M -XX:MaxNewSize=341M -XX:NewSize=341M -XX:MaxPermSize=1296M -XX:PermSize=512M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -XX:+HandlePromotionFailure -XX:+UseParNewGC -XX:+DisableExplicitGC -XX:+UseTLAB -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -verbose:gc -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -Djco.jarm=1 -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djava.security.policy=./java.policy
ID2849550.JavaPath=C:/j2sdk1.4.2_13-x64
ID2849550.LogName=server0
ID2849550.MainClass=com.sap.engine.boot.Start
ID2849550.MaxHeapSize=
ID2849550.Name=server0
If you notice here you can see that the -Xmx is still 0
The file is not getting saved (if you have pressed the save button) after modifying the parameter in the confogtool.
Backup the instance.properties file.
Edit the instance.properties file and 2048
Save the file and launch the configtool.
Start SAP.
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You may also refer to the suggestions provided in this SAP note 736557 - Changes made with the Config Tool are disregarded
Regards
RB
RB,
I made all the changes fine.
after restarted the SAP it failed.
1. In Instance.property file ID2849550.MaxHeapSize= again went 0.
2. When i save in Config tool the popup says - changes will take effect after restarts the Java server. but i saved.
3. In order to restart instance i am unable to log in visual admin.
4. In config tool i can see xms and max heap size are same value 2048M, is it okay?
Please help to solve this issue.
Regards,
Farkath C
You won't be able to login to Visual Admin until the system is up and running. Only Config Tool is going to work while it's down. What release of NetWeaver is this, by the way?
Are you completely shutting down SAP in the MMC, and restarting the service via Computer Management or Control Panel... Services?
Heap size is changed from configtool.
Also system should be running to connect to VA
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
since you are running vendor JVM.
Refer:723909 - Java VM settings for J2EE 6.40/7.0
or 1248926 for 7.1
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.