Discussion Feed

Peter.Holditch · ‎01-05-2021

Gabor, My bad, I missed the local-to-the-try-catch-block constructed Transaction object when I looked at your code. From your latest comments, it sounds as if this is working as expected. The 1st time your entry is called within a new process, the BT will register with the controller. Once that is done, subsequent invocations handled in the same process will be measured, and as those measurements are reported by the agent (once per minute) the data will become visible in the controller. I suspect you eventually amassed enough post-registration invocations and elapsed time for that to happen. Warm regards, Peter

Peter.Holditch · ‎01-04-2021

Hm, OK. Your code does. not show you calling endTransaction, but you do mention that in the subject. Are you certain your code is calling endTransaction? Also, how many times in the transaction you have instrumented being executed? Do you see it referenced if you remove the (default) filter for Transactions with performance data?

Peter.Holditch · ‎01-04-2021

2 thing to check: Are there any error or informational messages written in the agent log? Have you hit the node or application level BT limit? Warm regards, Peter

Peter.Holditch · ‎12-09-2020

Ahmed, Business transactions are identified by BT name and originating tier, so you will get one transaction per name per tier. What is your underlying motivation for splitting the nodes into different tiers? How do the loads differ? Warm regards, Peter

Peter.Holditch · ‎06-02-2020

The issue here is that "feed" is a valid hexadecimal number... If you're sure that your application never needs to interpret 'feed' as anything other than the word feed, you should be able to manage this situation with rule priorities. The higher priority rule should match "ends with hendelser/feed" and the lower priority one should be your regex match. That way, exact feed matches will never hit the second rule. The documentation shows you how to set rule priorites. Warm regards, Peter

Peter.Holditch · ‎05-07-2020

Do you have any output at all from the glassfish startup? When you say " the agent /opt/appdynamics/appagent/javaagent .jar is unzipped inside the container where glassfish is running" do you mean that the only file in the container is javaagent.jar? If so, that is the root cause of your issue. You need the entire agent directory structure as contained in the agent zip for the agent to function.

Peter.Holditch · ‎05-05-2020

Steven, A high level explanation is provided in the documentation: https://docs.appdynamics.com/display/PRO45/Java+Agent+Directory+Structure Warm regards, Peter

Peter.Holditch · ‎03-25-2020

Is the server hosted in a container? If so, you may have trouble with entropy. Try putting -D appdynamics.low.entropy=true on the JVM command line. If that does not help, can you post a thread dump taken from the JVM during startup? Warm regards, Peter

Peter.Holditch · ‎03-24-2020

AppDynamics' offers initial Oracle Java 14 Beta build certification test results with Java Agent v20.3.0 AppDynamics Java Agent v20.4.0 has been certified for AdoptOpenJDK, Azul Zulu Open JDK, Oracle, and Open Source Open JDK. See Java Supported Environments and watch this space for further updates Table of Contents Overview: Java 14 and AppDynamics Support Java 14 Beta build test results Overview Since September 2017, the Java roadmap includes LTS releases every 3 years in September with incremental releases in March and September, each with a 6 months support window. For AppDynamics, supporting a new Java version includes 2 aspects: Agent certification on the new release Product enhancements to leverage platform new capabilities. . AppDynamics Java 14 Support We intend to support Oracle Java 14 as soon as possible. The Java 14 beta drop passed all the validation tests with our publicly available Java Agent v20.3.0. Depending on further testing, we might announce formal Java 14 support with this 20.3.0 release or the 20.4.0 one currently scheduled for the 3rd week of April 2020. Java 14 Beta build test results Below is a representative sample of the initial validation tests conducted with the Java 14 Beta builds and their individual results. In summary, all these initial tests have passed successfully with Java 14 Beta builds. Test Result Application startup and Agent Registration Pass Simple Servlet Application deployed in Tomcat 9 Pass, verified for its startup, monitoring and metrics flow POJO application on AppDynamics Controller v20.3.0 Pass, verified the exchange of agent configurations with: Controller Flow map diagrams Metrics Snapshots capture Agent Logs Pass, no errors or exceptions occurred

Peter.Holditch · ‎03-17-2020

Rohde, Can I ask what kind of server-side projects you are developing using kotlin, and which frameworks you are using? Warm regards, Peter

Date Registered	‎01-23-2013 01:54 AM
Date Last Visited	‎01-13-2021 12:11 AM
Total Messages Posted	319
Total Kudos Received	93

Discussion Feed

Re: AppdynamicsAgent.startTransaction/endTransacti...

Re: AppdynamicsAgent.startTransaction/endTransacti...

Re: AppdynamicsAgent.startTransaction/endTransacti...

Re: business transaction per tier

Re: Regex for URL in Business Transaction

Re: Java Agent doesn't start in Docker container

Re: Multiple copies of files in Java Agent zip

Re: After Integrating with Appd, Ping Access is ta...

Java 14 Beta builds tested with AppDynamics Java A...

Re: Support for KOTLIN