Sailesh, Can you post your entire command line please, many things look off in the output you pasted. Did the agent start and work OK despite the original ERROR message? Warm regards, Peter ... View more

The documentation describes how to instrument tomcat here: https://docs.appdynamics.com/display/PRO45/Apache+Tomcat+Startup+Settings These instructions should help you get started. Warm regards, Peter ... View more

Anil, I have not seen this error before, but I suspect you can supress it by excluding instrumentation of the com.tangosol.net package. If you look in /u01/app/AppServerAgent/ver4.5.7.24863/ you will find a file called app-agent-config.xml In there, you will see a line saying: <agent-service name="BCIEngine" enabled="true"> beneath this, you will see <bci-processing-excludes> and under there lines like <custom-exclude filter-type="STARTSWITH" filter-value="io/netty/util/concurrent/SingleThreadEventExecutor"/> if you add this: <custom-exclude filter-type="STARTSWITH" filter-value="com/tangosol/net/"/> and restart, you should find the process starts fine. Please let me know if this helps. Warm regards, Peter ... View more

Shritha, I think you need to split on segment 5 instead of segment 6. Please let me know if that helps. warm regards, Peter ... View more

One imediate thought:  Can you apply a POCO entry point to all the specific command classes, if all the interesting work happens within them? Warm regards, Peter ... View more

The package qualifiers limit increase should resolve the issue. We will need agent logs to investiagte why this has not happened in your case; the best way to share these would be via a support ticket. Warm regards, Peter ... View more

One database agent hosting 2 configured collectors is the expected deployment model. The documentation describes this here. Warm regards, Peter ... View more

I suspect in this case that the exit to the database (which is the instrumented method) is being called multiple times within the higher levels of the database driver as it iterates across the large result set you are retrieving. In that case, you see one entry in the snapshot per iteration. ... View more

That response at least validates your agent installation. Looking at the rest of your command line, the double quotes in this section "-javaagent:C:\Users\prubin.INGRNET\eclipse\jee-2018-09\eclipse\configuration\org.eclipse.osgi\1008\0\.cp\lib\javaagent-shaded.jar" look suspect.  Can you remove them? Am I correct to understand that with the changed slashes, your agent is now working? ... View more

wow! What happens if you run C:\Program Files\Java\jdk-11.0.1\bin\javaw.exe -javaagent:/Users/prubin.INGRNET/Downloads/AppServerAgent-4.5.6.24621/javaagent.jar -version ... View more

That should be fine then; can you share the full JVM command line? ... View more

Paul, What version of the java agent are you using?  Java 11 support was ony added in 4.5.5 so no earier version will work in this scenario. Warm regards, Peter ... View more

The WebSphere issue here is that the classes being instrumented are loaded by some OSGi framework. You need to configure boot delegation as documented here. Warm regards, Peter ... View more

I'm delighted you got things working! The install.dir property should not be mandatory, so I will look in to why that seems to be needed in your case. I hope you enjoy the rest of your evaluation experience! ... View more

With the -javaagent option corrected, the next step is to look at the agent logs and see what is written in there. Another trick is to run a simple smoke test: "java -javaagent:<path to agent> -version If this prints the java version successfully, it will also have started the agent on your machine, which will have written some logs.  These may also contain clues as to what is going on. Warm regards, Peter ... View more

You have the command line option wrong... You have typed -Djavaagent:C:/ABHIROOT/... It shoud just be -javaagent:C:/ABHIROOT/... warm regards, Peter ... View more

Anand, What you are describing is basically the intent of the call graphs within our BT snapshot feature.  Have you looked into that? Warm regards, Peter ... View more

Anand, You are corect that, being a real-time APM solution, we do not provide forensic heap dump analysis capabilties. We do, however, provide a set of memory diagnostic capabiltiies to help you pinpoint the root cause of memory leaks; these capabilities are documented here. Warm regards, Peter ... View more

Clyde, You appear to be trying to start a war file directly.  You need to start the tomcat instance that hosts it with the tools.jar available. Warm regards, Peter ... View more

By insufficient permissions, do you mean that you see an HTTP 401 response logged in the agent log? If so, it is likley that you are not passing the correct application key to the agent, have you double-checked that? ... View more

Is the code retrieving some kind of large result set from the database? If so, that would probably explain what you're seeing. ... View more

Ah, sorry.  I had missed your earlier comment. Often customers find that the security fixes contained within each update release as a good motivator for justifying upgrades the producton JVM estate. That said, I understand how frustrating it is to need to push through a production JVM upgrade without absolute certainty that it will fix a crash issue.  For what it's worth, in my experience, that is the outcome in the vast majority of cases, Warm regards, Peter. ... View more

Erik, The AppDynamics java agent never looks in logs for errors, it intercepts them being logged by instrumenting logging frameworks. I think its quite unlikely that changing the error detection rules would have an impact on JVM crash behaviour. Did you try upgrading the JVM? ... View more