Discussion Feed

If an application is using org.springframework.aop.interceptor.AsyncExecutionInterceptor$1  classes while making asynchronous calls, then follow these steps to track the activities inside these calls.   1.Open the  <agent-install-dir>\ver4.x.x.x\conf\app-agent-config.xml file 2.Navigate to the <fork-config>  section of the XML file. 3.Add the following entry:    <include filter-type="STARTSWITH" filter-value="org. springframework.aop. interceptor/"/>   4.Save the changes  5.Restart the JVM to take changes into effect.   ... View more

When configuring an AppDynamics Java Agent on a Tomcat server with Felix framework, some users ran into the following error message:    java.lang.NoClassDefFoundError: com/singularity/ee/agent/appagent/entrypoint/bciengine/FastMethodInterceptorDelegatorBoot  at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java)  at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)    This error is due to missing the following configurations which apply to the Felix framework.   Navigate to the <Tomcat-install-dir>/webapps/ROOT/WEB-INF/etc/config folder. Edit the file felix-framework.properties Search for the property org.osgi.framework.bootdelegation" property Add com.singularity.* to this property. Example: org.osgi.framework.bootdelegation=sun.*,com.sun.*,com.sun.jndi.ldap,com.yourkit.*,__redirected,com.singularity.*      ... View more

To establish the correlation between tiers or applications, AppDynamics generates a "singularity header" which is passed to a downstream node.   In some cases, the JMS payload is not allowed to write any data to the JMS message,  correlation behavior is impacted,  and the following error message appears in logs.   17 Jul 2017 12:49:03,065 ERROR ReadonlyRewriting_JMSMessageReflector - MessageNotWriteableException caught while setting transaction header. To attempt modification of the read-only JMS message, add the object's package (org.apache.activemq.ra) to the jms-packages-allowed-for-rewriting node property.   To resolve this issue, create a node property  jms-packages-allowed-for-rewriting  and change the JMS package name to the value of this property. This will ensure that JMS allows writing to the singularity header on JMS payload objects.   Example:    Property Name : jms-packages-allowed-for- rewriting Type: String Value :org.apache.activemq.ra       ... View more

As seen in the CometD Support documentation, POJO transactions are identified out of the box on CometD applications. The business transactions are identified and split based on the channel names. In some scenarios, this may lead to business transaction explosion. To prevent this, define some custom POJO rules.   Define POJO rule based on the following class & method: Class: org.cometd.server.BayeuxServerImpl Method: doPublish Apply the split rule based on requirement.     ... View more

Problem   Users with on-premise Controllers using Java Machine Agents report that no hardware metrics are showing on the Controller UI.   To troubleshoot this issue, review the Machine Agent logs. The following error message indicates that the Agent is not able to publish the metrics:   [Worker-2] 16 Mar 2017 07:56:38,042 WARN MetricOutputHandler - Metric Reporter type mismatch for metric [Hardware Resources|CPU|%Idle] com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricReporterTypeMismatchException: Aggregator of AVERAGE already exists for metric Metric Identifier[Hardware Resources|CPU|%Idle] ID[0] [Worker-2] 16 Mar 2017 07:56:38,042 WARN MetricOutputHandler - Metric Reporter type mismatch for metric [Hardware Resources|CPU|%Busy] com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricReporterTypeMismatchException: Aggregator of AVERAGE already exists for metric Metric Identifier[Hardware Resources|CPU|%Busy] ID[0]     Solution   First, verify that both of the monitors are enabled within the monitor.xml file, which is located at  <machine-agent-install-dir>\monitors\JavaHardwareMonitor\monitor.xml  and  <machine-agent-install-dir>\monitors\HardwareMonitor\monitor.xml  .   If both monitors are enabled, disable the JavaHardwareMonitor property by configuring the enabled flag with a value of "false" in the \JavaHardwareMonitor\monitor.xml file.   Then restart the Machine Agent's  Java process.   ... View more

The Java Agent has been configured on an IBM Server and the following error messages are appearing in the application log files:    ERROR UserInterface Displaying to the user an exception message that is not a UserDisplayableException java.lang.VerifyError: JVMVRFY012 stack shape inconsistent; class=gw/api/exposure/ExposureAssignmentPopup, method=<init>([Lcom/guidewire/cc/domain/exposure/ExposureAbstractView;)V, pc=79   To resolve this issue, start the application with the following parameter:    -XX:-UseSplitVerifier -Xverify:none             ... View more

In order to view the SQL statements in transaction snapshots related to Postgres database, apply the following node properties.    See: How to Add a Registered Node Property   Property: jdbc-connections Value: org.postgresql.jdbc.PgConnection Property: jdbc-statements Value: org.postgresql.jdbc.PgStatement Property: jdbc-callable-statements Value: org.postgresql.jdbc.PgCallableStatement Property: jdbc-prepared-statements Value: org.postgresql.jdbc.PgPreparedStatement ... View more

Problem:   Users find JNI-related warning messages in application logs.    Example:   WARNING: JNI local refs: 76306, exceeds capacity: 32 at sun.instrument.InstrumentationImpl.getAllLoadedClasses0(Native Method) at sun.instrument.InstrumentationImpl.getAllLoadedClasses(InstrumentationImpl.java:176) at com.singularity.ee.agent.appagent.services.bciengine.B.a(B.java:135) at com.singularity.ee.agent.appagent.services.bciengine.B.b(B.java:194) at com.singularity.ee.agent.appagent.services.bciengine.B.c(B.java:268) at com.singularity.ee.agent.appagent.services.bciengine.asm501.B.a(B.java:1003) at com.singularity.ee.agent.appagent.services.bciengine.asm501.B.c(B.java:976) at com.singularity.ee.agent.appagent.services.bciengine.asm501.B.a(B.java:56) at com.singularity.ee.agent.appagent.services.bciengine.asm501.H.a(H.java:156) at com.singularity.ee.agent.appagent.services.bciengine.asm501.B.a(B.java:632) at com.singularity.ee.agent.appagent.services.bciengine.asm501.B.a(B.java:860)     Solution:   1. Restart the JVM without the  Xcheck:jni  parameter  or 2. Change the JVM to JDK 8u65 or 8u60  Related Links: JDK bug system: Excessive checked JNI warnings from Java startup JDK bug system: -Xcheck:jni improvements to exception checking and excessive local refs ... View more

Users with applications using a  java.util.concurrent.Future package while making asynchronous calls can track their async call activity as follows:   Open the Application Agent config file located at  <agent-install-dir>\ver4.x.x.x\conf\app-agent-config.xml. Navigate to the <fork-config> section. Add the following to the end of the fork config section:  <job> <match-class type="implements-interface"><name filter-type="EQUALS" filter-value="java.util.concurrent.FutureTask"/></match-class> <match-method><name filter-type="EQUALS" filter-value="run"/></match-method> <name-config operation="" type="4"/> </job>       4. Save changes and r estart the JVM.     Note:  Certain resource-intensive AppDynamics features, such as asynchronous transaction tracking, can increase resource consumption. AppDynamics recommends that you monitor the memory consumption of your application to ensure that there are sufficient resources allocated to it.   ... View more

Rulebooks are core to Universal Agent functionality. If rulebooks are not formatted properly, Universal Agent behavior is impacted when deploying Java or Machine agents.   Use a JSON validator, such as JSON Lint, to ensure the rulebooks are formatted correctly.     Related Links: Universal Agent Rulebooks AppDynamics Universal Agent documentation New in 4.3 - Universal Agent ... View more