AppD Archive

Java.lang.Object:wait - Not able to pin point bottleneck

Vaibhav_Vir_Sin
Communicator

Hi Experts,

I am stuck with BW instrumentation where it seems some HTTP request is made which is not getting captured in snapshot.

Attached is the snapshot, where if you look at, I am not able to get what is this "wait" object method is.

I enabled java.lang.* from configuration-instrumentation. But still the same.

Cross jvm tracing is also working, but it seems it is not able to pick up the service name.

Please suggest.

Regards,

Vaibhav

0 Karma

Arun_Dasetty
Super Champion

Hi Vaibhav,

Not all methods will be shown in even full graph when methods are taken less than 10 ms and we understood the target exit calls are not under "async activity" in call graph and regarding your query on what is wait it could be that thread is in waiting for some other resource as such

But to confirm if any other packages are part of package excludes, Can you click link "packages excluded from the call graph" which will be at bottom of the call graph screen and force those packaes in includes and see if you get more visibility for new snapshots?

https://docs.appdynamics.com/display/PRO41/Configure+Call+Graphs#ConfigureCallGraphs-CallGraphGranul...

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Dynamic formatting from XML events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...