We've got Appdynamics agents installed on the Weblogic JVMs for an application. This app makes LDAP calls to multiple Microsoft AD Domain Controllers for authentication using DNS load balancing. We know from Weblogic logs, that these calls are occasionally timing out and causing thread locks in Weblogic, but we haven't been able to match up timestamps closely enough to track down which DCs are causing the time out.
I do not see any of the LDAP calls showing up in the Appdynamics dashboard or transaction snapshots. Is Appdynamics able to track these transactions, and if so, what do we need to do to make them visible?
Hi,
Is the business transaction (class and method) making LDAP Exit calls are part of "Business transactions" screen under the associated application in controller UI? If yes , Can you define LDAP Custom exit points as stated in doc section and see how it goes:
https://docs.appdynamics.com/display/PRO39/Configure+Custom+Exit+Points
By default we expect the exit calls to be ootb discovered if instrumented agent supports but if we do not see exit points as such we can define CEP as stated in above doc to monitor as expected. Keep us posted the agent logs and BT flow view and CEP configurationd defined if issue still persists to debug further.
Please be sure that CEP might require agent reset/restart if JVM is 1.5 version. Hope that information helps.
Regards,
Arun