Unable to login in Visual Administrator

[farkathulla_cikkanther]

  Hi Experts,

I am unable to login in Visual Admin. in order to troubleshoot MAX Heap size.

In SAP MMC, java server service is stopped.

In Visual admin, we are facing, attached the screenshot.

Please find trace file log for java serer service.

Best Regards

Farkathulla

trace file.txt.zip

[Reagan · Accepted solution]

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.

[farkathulla_cikkanther · Accepted solution]

Friend,

    We changed Max heap size to 2048 and rebooted system but still we are facing same issue.

Configtool settings:

attached trace file also.

Regards,

Farkath C

trace file2.txt.zip

[Reagan · Accepted solution]

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

[farkathulla_cikkanther · Accepted solution]

RB,

Sorry I suppose to attach config tool. Please find.

Regards,

Farkath

[divyanshu_srivastava3 · Accepted solution]

Remove 0 from xmx on all server nodes

[Reagan · Accepted solution]

Remove -Xss2M and save.

Restart the J2EE

[farkathulla_cikkanther · Accepted solution]

Divyan,

   Can you please tell me in detail where I have to change 0 from xmx. I could not find in Config tool.

Regards,

Farkath C

[farkathulla_cikkanther · Accepted solution]

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

[Reagan · Accepted solution]

Set the parameter Max Heap Size to 2048 and click on the save icon at the top.

Once it has been saved open the MMC and stop the SAP completely if there are some processes running.

Start the SAP J2EE system.

Upload the latest trace file.

[Reagan · Accepted solution]

Could you tell me what version of the JDK are you using ?

Are you using the SUN JDK or the SAP JVM ?

RB

[farkathulla_cikkanther · Accepted solution]

RB,

   I think we using - j2sdk1.4.2_13-x64.

Regards,

Farkath C

[divyanshu_srivastava3 · Accepted solution]

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

[Matt_Fraser · Accepted solution]

This is a very, very old JDK.  Once you have resolved this issue, you are going to want to convert to the SAP JVM.  However, you need to fix the -Xmx0m problem first.

[farkathulla_cikkanther · Accepted solution]

Divyan,

  Please find the attachment instance.properties,

there I cant find the parameter -xmx0M.

make this entry in instance.properties -xmx2048M will work?

Regards,

Farkath

instance.properties.txt.zip

[farkathulla_cikkanther · Accepted solution]

RB,

I fallowed what you said above but still error occurs.

Please find the trace file attachment.

Regards,

Farkath C

trace file3.txt.zip

[divyanshu_srivastava3 · Accepted solution]

Hi,

Can you give me remote session of your system using team-viewer, i will try to fix it.

Regards

[divyanshu_srivastava3 · Accepted solution]

Hi,

Follow these step.

Stop SAP

open configtool. Recheck and add -Xmx2048M.

Save and exit

goto /usr/sap/SID/j2ee/cluster

rename instance.properties.vmprop to instance.properties.vmprop.old

rename  instance.properties to  instance.properties.old

Now start SAP.

Share results.

Divyanshu

[Matt_Fraser · Accepted solution]

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

[farkathulla_cikkanther · Accepted solution]

Divyan,

  configtool. Recheck is not in my system.

Where it could be?

Reg,

Farkath C

[divyanshu_srivastava3 · Accepted solution]

i mean to save open configtool---- then recheck the values----- save it

[farkathulla_cikkanther · Accepted solution]

Divyan,

In Configtool Xms2048M is exist,

Can you please confirm Xmx2048M have to create?

Reg,

Farkath C

[divyanshu_srivastava3 · Accepted solution]

Yes, xms mean initial and xmx means maximun.

[farkathulla_cikkanther · Accepted solution]

Matt,

   I can see the parameters like below different areas,

Please let me know do i have to change any value.

Regards,

Farkath C

[farkathulla_cikkanther · Accepted solution]

Divyan,

  Initial and Max can be same? because Xms already exixt with the value 2048M.

Reg

Farkath C

[Matt_Fraser · Accepted solution]

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).

[Reagan · Accepted solution]

Can you make the changes based on what Matt suggested?

I can see that -Xms and -Xmx are configured with 1024M of heap size under the "Servers General"

[divyanshu_srivastava3 · Accepted solution]

yes..

[farkathulla_cikkanther · Accepted solution]

Fixed. thank u.

Farkath C

[Reagan]

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

[Reagan]

You may also refer to the suggestions provided in this SAP note 736557 - Changes made with the Config Tool are disregarded

Regards

RB

[farkathulla_cikkanther]

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

[divyanshu_srivastava3]

Give me the access

My mail ID is in my profile.

Divyanshu

[Matt_Fraser]

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?

[divyanshu_srivastava3]

Fixed with changes that I suggested above

[divyanshu_srivastava3]

Heap size is changed from configtool.

Also system should be running to connect to VA

[divyanshu_srivastava3]

The problem is with "-Xmx0M" parameter.

Goto configtool and make changes, give some value to this.

Refer guidelines as per OS and version.

Divyanshu

[divyanshu_srivastava3]

set 2048 for now and then configure as per your OS and version.

[divyanshu_srivastava3]

since you are running vendor JVM.

Refer:723909 - Java VM settings for J2EE 6.40/7.0

or 1248926 for 7.1