Only "standard" Introscope Metrics show up
When looking with the Investigator to the metrics of a java agent you find that only few "standard" Introscope metrics like EM Host, EM Port, Host, GC Heap are reported but no other metrics appear which you expect to see (e.g. SAP J2EE).
In the IntroscopeAgent.log you also see that the number of metrics that are send to the EM is quite low (< 100). For a J2EE server node the metric number is usually higher than 1000.
Java server node does not come up
If agent on the fly is used in combination with switching a managed system between different different physical hosts then the byte code adapter must be installed under the instance directory of the managed system. This can be achieved by turning on the flag Ensure HA compatibility and entering a custom deployment path. Note that typically this folder must be created manually since the diagnostics agent does not have write permission. See also Diagnostics Agent and HA Support.
Missing log files
In std_server.out you can see this exception:
java.io.FileNotFoundException: /usr/sap/<SMD_AGENT>/temp/IntroscopeAgent.log (Permission denied)
User <sid>adm does not have write permission in SMD Agent folder.
Set umask as described in note 1163751.
High CPU load when BCA is active
After activating the bytecode agent the CPU consumption of the managed system increases dramatically ( eg. from 3% to 50%). The problem occured so far only on the platforms
- Windows Server 2008 64bit
- Windows 7 64bit (not officially supported for Introscope agents)
Workaround: Deactivate the Platform Monitor by deleting the following files:
- introscopeWindowsIntelAmd64Stats.jar in directory usr/sap/<AGENT_SID/<instance>/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.<current_version>/wily/ext Solution: replacement files for the dlls listed above are attached to Note 1273028 (PM_Fix_Binaries.zip)
Agent Version 220.127.116.11 build 476364 with a build date from July 2010
Check the property introscope.autoprobe.directivesFile in the IntroscopeAgent.profile which is set by the java parameter -Dcom.wily.introscope.agentProfile
Either no intrumenation files are set with property introscope.autoprobe.directivesFile or you find there a variable like #WILY_IS_AUTOPROBE_DIRECTIVES# instead of concrete intrumentation files.
For the latter see note 1273028: upgrade to ISAgent Release 8 SP2 patch2 (since patch1 was buggy) and rerun the automatic agent setup again
Agent Version 18.104.22.168, build 476583, 20110526)
In the Autoprobe.log the following error is mentioned:
Can't proceed because the flag "JSF_Application_ViewHandlerTracing" is never declared
Solution: Apply either patch 4 of 22.214.171.124 or version 126.96.36.199
Agent Version 188.8.131.52, build 476771, 20120125)
In the IntroscopeAgent.log the following error is mentioned:
[ERROR] [IntroscopeAgent] The agent extensions directory /usr/sap/.../SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.184.108.40.206-2012-01-27/wily/core/config/ext could not be located. No extensions will be loaded.
Solution: Apply patch 1 of 220.127.116.11.
Release 8 SP24 patch 1 (File name ISAGENT24P_1-10007435.SCA, Introscope Version 18.104.22.168, build 476771, 20120626)