Symptom
When running activity "Byte Code Adapter Installation", a warning is shown, but no details are provided, other than "Remote operation completed with warnings":
If you set the SMDAgentApplication log to debug, you may find the following error stack:
[Thread[ExRun:default_2,5,default:ExecTG] ] Error [WHS] Failed to find javaPath for node <number>
[EXCEPTION]
com.sap.smdagent.vmmanager.VMManagerException: Failed to use JMX service
at com.sap.smdagent.vmmanager.impl710.VMManager711._getSettings(VMManager711.java:215)
at com.sap.smdagent.vmmanager.impl700.VMManager.getSettings(VMManager.java:136)
at com.sap.smd.helper.j2ee.J2eeNodeIntrospector.getJavaPath(J2eeNodeIntrospector.java:44)
at com.sap.smd.wily.WilyHandlerService.performCommonSteps(WilyHandlerService.java:1231)
at com.sap.smd.wily.WilyHandlerService._configureISAgent(WilyHandlerService.java:1156)
at com.sap.smd.wily.WilyHandlerService.access$000(WilyHandlerService.java:61)
at com.sap.smd.wily.WilyHandlerService$2.run(WilyHandlerService.java:535)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:94)
at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:285)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
at java.lang.Thread.run(Thread.java:763)
Caused by: com.sap.smdagent.plugins.connectors.jmx.exc.RemoteJmxException: getAttributes; nested exception is:
com.sap.smdagent.plugins.connectors.jmx.exc.RemoteJmxException: Runtime exception in connector occurred; nested exception is:
com.sap.smdagent.plugins.connectors.jmx.exc.RemoteJmxException
at com.sap.smd.agent.plugin.connectors.jmx.JmxProxy.getAttributes(JmxProxy.java:344)
at com.sap.smdagent.vmmanager.impl710.Utils.getInstanceTemplateObjectNames(Utils.java:81)
at com.sap.smdagent.vmmanager.impl710.VMManager711.getInstanceObjectName(VMManager711.java:64)
at com.sap.smdagent.vmmanager.impl710.VMManager711._getSettings(VMManager711.java:184)
... 16 more
Caused by: com.sap.smdagent.plugins.connectors.jmx.exc.RemoteJmxException: Runtime exception in connector occurred; nested exception is:
com.sap.smdagent.plugins.connectors.jmx.exc.RemoteJmxException
at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invokeMbsInternal(MBeanServerConnectionImpl.java:560)
at com.sap.engine.services.jmx.MBeanServerConnectionImpl.getAttributes(MBeanServerConnectionImpl.java:345)
at com.sap.smd.agent.plugin.connectors.jmx.JmxProxy.getAttributes(JmxProxy.java:340)
... 19 more
Caused by: com.sap.smdagent.plugins.connectors.jmx.exc.RemoteJmxException
at com.sap.pj.jmx.server.MBeanServerImpl.getAttributes(MBeanServerImpl.java:1346)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttributes(MBeanServerWrapperInterceptor.java:192)
at com.sap.engine.services.jmx.CompletionInterceptor.getAttributes(CompletionInterceptor.java:311)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttributes(BasicMBeanServerInterceptor.java:180)
at com.sap.jmx.provider.ProviderInterceptor.getAttributes(ProviderInterceptor.java:247)
Some additional details will be found if you click on "Open Java URL", right beside the "Byte Code Adapter Installation", in the managed system configuration. A new screen will be shown, where you can try to perform the installation by selecting the agent, and clicking on "Configure Introscope Agent Setup", then choose "Apply", like below:
Read more...
Environment
SAP Solution Manager 7.1, performing the managed system configuration for a system on 7.10.
Product
Keywords
"VM parameters update" , KBA , SV-SMG-DIA-WLY-BCA , Byte Code Agent Setup , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview