cancel
Showing results for 
Search instead for 
Did you mean: 

Error while Byte Code Adapter Installation SM 7.1 SP4

Former Member
0 Kudos
209

Hello everyone,

I have an issue with Byte Code Adapter installation on my solution manager:

Failed to update VM parameters - com.sap.smdagent.vmmanager.VMManagerException: A test vm could not be started, the vm parameters seems to be incorrect:-Xss2M -XX:MaxNewSize=341M -XX:NewSize=341M -XX:MaxPermSize=512M -XX:PermSize=512M -XX:ReservedCodeCacheSize=64M -XX:CodeCacheMinimumFreeSpace=2M -XX:CompilerThreadStackSize=4096 -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 -XX:+JavaMonitorsInStackTrace -Dcom.wily.introscope.agent.agentName=ASM_DVEBMGS00_server0 -Dcom.wily.introscope.agentProfile=D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.0-2012-01-27/wily/IntroscopeAgent.profile -Xbootclasspath/p:D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.0-2012-01-27/wily/connectors/AutoProbeConnector.jar;D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.0-2012-01-27/wily/Agent.jar
Output:Error occurred during initialization of VM
Incompatible initial and maximum heap sizes specified

Error:

I changed Xms parameter to -Xms1048M for my instance using config tool. Max heap size (in MB) is set to 2048. After changes I restarted ICM Java cluster using SMICM tcode (Send hard Shutdown-> With restart). After that i tried again but no luck. Please advise.

BR,

SAPfan

Accepted Solutions (1)

Accepted Solutions (1)

hugo_amo
Employee
Employee
0 Kudos

Hi SAPFan,

Try this:

1 - Open Agent administration UI on Solution manager

2 - Navigate to The "Applications Configuration" tab

3 - Choose on the left the

application "com.sap.smd.agent.application.connectors"

4 - Edit the property "vmmanager.test.vm.before.update" and set the

value to false. (DO NOT USE SCOPE GLOBAL, SELECT THE RIGHT AGENT)

5 - Save the properties.

Regards,

Hugo

Former Member
0 Kudos

Hello Hugo ,

Thanks a lot for solution it works.

BR,

SAPFan

hugo_amo
Employee
Employee
0 Kudos

Hi!

Very glad to hear it

Have a nice day.

Hugo

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

We saw a similar error while switching the JVM from a Sun JVM to SAP JVM, the cause of the issue in this cause was that there was not sufficient free memory on the server to start an additional VM (the test VM).

I our scenario we had more than one SAP instance running on the server, therefore we stopped one of the other instances and re-run our JVM switch.

It may be worth you checking the free memory available on the server to see if you have sufficient memory to start another VM and/or stopping any application or service to free memory and then re-run the byte code adapter installation.

Regards


Ryan