APM for Java AppDynamics Pro Documentation Version 4.0.x Page 1 APM for Java . 4 Configure Java Monitoring . 4 Refine Business Transaction Discovery . 5 Java Web Application Entry Points . 9 Servlet Entry Points . 10 Automatic Naming for Servlet Business Transactions . 12 Custom Naming for Servlet Business Transactions . 20 Custom Expressions for Naming Business Transactions . 31 Advanced Servlet Transaction Detection Scenarios . 32 Struts Entry Points . 45 Web Service Entry Points . 47 POJO Entry Points . 49 Spring Bean Entry Points . 57 JMS Entry Points . 60 EJB Entry Points . 61 Binary Remoting Entry Points for Apache Thrift . 64 CometD Support . 67 Mule ESB Support . 68 JAX-RS Support . 69 Spring Integration Support . 70 Exclude Rule Examples for Java . 72 Configure Multithreaded Transactions for Java . 75 Configure End-to-End Message Transactions for Java . 77 Configure Backend Detection for Java . 79 Custom Exit Points for Java . 86 HTTP Exit Points for Java . 97 JDBC Exit Points for Java . 102 Message Queue Exit Points for Java . 107 Web Services Exit Points for Java . 113 Cassandra Exit Points for Java . 114 RMI Exit Points for Java . 115 Thrift Exit Points for Java . 116 Configure Memory Monitoring for Java . 116 Automatic Leak Detection for Java . 116 Object Instance Tracking for Java . 118 Custom Memory Structures for Java . 120 Configure Java Background Tasks . 127 Getter Chains in Java Configurations . 128 Instrumenting Java 8 Constructs . 134 Code Metric Information Points for Java . 139 Configure JMX Metrics from MBeans . 139 Create and Import or Export JMX Metric Configurations . 147 Exclude JMX Metrics . 149 Exclude MBean Attributes . 150 Configure JMX Without Transaction Monitoring . 151 Resolve JMX Configuration Issues . 151 MBean Getter Chains and Support for Boolean and String Attributes . 156 Monitor JVMs . 159 Troubleshoot Java Memory Leaks . 166 Troubleshoot Java Memory Thrash . 172 Monitor Java App Servers . 178 Monitor JMX MBeans . 179 Page 2 Detect Code Deadlocks for Java . 189 Trace Multithreaded Transactions for Java . 191 Troubleshoot Slow Response Times for Java . 197 Page 3 APM for Java Once your Java application environment is instrumented with the AppDynamics Java Agent, you can start monitoring Java application performance. For general information on configuring AppDynamics deployment, see the topics under AppDynamics Essentials. This section describes considerations specific for monitoring Java applications. It also describes how to fine tune the configuration for specific Java frameworks and technologies. These include, for example, monitoring and configuration topics for JVMs, Java application servers, and JMX. Get a PDF version of the Java Monitoring documentation. Learn by watching End-to-end APM for What's New in 4.0? Application Intelligence Java Platform: A Quick Tour A new directory structure to More videos... Java Supported enable drop in upgrades Environments Business transaction lock down Install a Controller or get a Cross-application correlation SaaS Controller New Framework support: Instrument Java WebMethods Applications Tibco Monitor JVMs SLF4J, Log4j 2, Logback Monitor Java App Servers instrumentation See more in the release notes Configure Java Monitoring After instrumenting your Java applications with the AppDynamics agent and connecting the agent to the AppDynamics Controller, you can start monitoring your application environment right away. The AppDynamics platform gives you insights into your environment right away. It automatically bu ilds a model of your environment, detects business transactions, and measures performance. Over the course of monitoring, however, it's likely that you will want to tweak and refine aspects of the default AppDynamics behavior, such as how your business transactions are modeled. You may also want to extend monitoring to processes that are not instrumented by default, such as background processes. AppDynamics gives you significant control over how these things are done. Configuring AppDynamics and, as described here, Java monitoring in particular, is often an iterative, on-going process, especially as new applications come online or as there are changes to your application environment. The Java monitoring topics covered here are: Copyright © AppDynamics 2012-2015 Page 4 Refine Business Transaction Discovery Java Web Application Entry Points Exclude Rule Examples for Java Configure Multithreaded Transactions for Java Configure Backend Detection for Java Configure Memory Monitoring for Java Configure Java Background Tasks Getter Chains in Java Configurations Instrumenting Java 8 Constructs Code Metric Information Points for Java Configure JMX Metrics from MBeans See also, Java Agent Configuration Properties Refine Business Transaction Discovery On this page: Start a Transaction Discovery Session Working with the Transaction Discovery Tool Rate this page: The default transaction discovery capabilities in the AppDynamics platform can get you up and running quickly. However, in most cases, you will want to tune and refine how business transaction are discovered. This ensures that the business transactions you are monitoring are those that reflect the traffic that is most important to you. The Transaction Discovery tool is designed to help with this. It lets you refine business transaction discovery. During a Business Transaction Discovery session, you can see the effect of the changes you make to the configuration without having to apply it to the active configuration. When you've finished making your changes, you can then choose which tiers of the application to apply the tuned configuration to or not apply the changes at all. Start a Transaction Discovery Session 1. From the left navigation menu, click Configure->Transaction Discovery and then click Sta rt Discovery Session. 2. Select the nodes for which you want to configure business transaction discovery and then click OK. You can choose to run the discovery session on more than one node, using Shift-click to select successive nodes, but all the nodes selectect must be within the same tier. At the end of the configuration process you can apply your transaction detection configuration changes to one or more tiers. AppDynamics starts discovering transactions and displays them as soon as they are detected. 3. Copyright © AppDynamics 2012-2015 Page 5 3. During discovery, you can use other features of AppDynamics while the discovery process continues in the background. You may want to do this in a busy environment where many transactions are happening. You can give AppDynamics a few minutes to complete the discovery and then return to the Transaction Discovery page by clicking Configure->Transa ction Discovery. As discovery occurs, the Transaction Discover page lists the transactions. A transaction summary shows how many transactions were found by type, as follows: From the list you can determine whether there are some transactions that are not being monitored. For these, you can create a custom match rule to identify those transaction types on the Edit Discovery Config tab. For transactions that you don't want to trace, create a custom exclude rule on Edit Discovery Config tab. The page show the list of transactions, their type, discovery timestamp (when first detected), load (total number of calls of the business transaction since the discovery timestamp), and more. Working with the Transaction Discovery Tool While your transaction discovery session is running, you can perform the following operations. Stop Session Clicking Stop Session exits the Business Transaction Discovery tool without saving any of the changes you made Reset Data Clicking Reset Data clears the window and initiates a new business transaction discovery session. The information displayed in the previous discovery session is not saved. View Snapshot A snapshot of the transaction provides you with details about the transaction that can help you decide whether or not you want to monitor this transaction type or any of the methods executed by the transaction. 1. Copyright © AppDynamics 2012-2015 Page 6 1. On the Transaction Discovery window, select a transaction for which transaction snapshots are supported. For example, AppDynamics doesn't take snapshots of Struts Action transactions but it does for Servlet transactions. Click View Snapshot The snapshot window appears. It will be empty at first but then will fill up as snapshots are taken. It will continue to take snapshots until you stop the discovery session. Click Clear Snapshots to restart the snapshot session and delete details of snapshots taken in the previous session. 2. Click a snapshot and then click View Snapshot to view the captured details of the transaction. The information displayed on this page can help you create transaction match and exclude rules. After viewing the details of that snapshot you can click the breadcrumb to return to the snapshots page where you can choose to view the details of another snapshot. Use the Class/Method Browser The Class/Method Browser allows you to filter the classes of the transactions that have been discovered for only those classes that meet specific criteria. Knowing which classes and methods are being traced can help you create custom match or exclude rules. such as by providing you with information you could use to complete the fields on the Split Transactions Using Payload tab of the New Business Transaction Match Rule for a Servlet. The information presented here can also help you identify transactions that are not being traced, in which case you would create a custom match rule to include transactions of that type. To filter the classes shown.