Hello Hari Shree, Thank you for your request to our community. We are happy to assist you with this matter. It seems you are running Java app in a dynamic environment. In dynamic environment, the vanilla agent in each container will register as a separate node, so such situation occurs. You need to add configuration in the dynamic environment as follows. [JVM properties] -Dappdynamics.agent.reuse.nodeName=true -Dappdynamics.agent.reuse.nodeName.prefix=<YOUR PREFIX HERE> -Dappdynamics.jvm.shutdown.mark.node.as.historical=true You can also set the above parameter in your <agent-dir>/verx.x.xxx/conf/controller-info.xml or app-agent-config.xml. Please refer the document below. https://docs.appdynamics.com/display/PRO45/Java+Agent+Configuration+Properties#JavaAgentConfigurationProperties-reusenodenameReuseNodeName https://docs.appdynamics.com/display/PRO45/Instrument+JVMs+in+a+Dynamic+Environment#InstrumentJVMsinaDynamicEnvironment-configuredynamic The last property is necessary for marking the node historical as soon as they are terminated. Please refer the document below: https://docs.appdynamics.com/display/PRO45/Instrument+JVMs+in+a+Dynamic+Environment#InstrumentJVMsinaDynamicEnvironment-MarkingDynamicNodesasHistoricalatShutdown If you have already set the above properties and the problem still remains, please make sure whether your application environment abortively terminates JVMs rather than allowing them to shut down gracefully or not. Because in this case, the terminated node is not marked as historical. As a result, it sometimes happen that the node name is not reused. Best regards, Yusuke ... View more

Hello Amritesh, Thank you for your request to our community. We are happy to assist you with this matter. Please make sure the following items. 1. Please confirm that you set <controller-host> in '<agent_home>/verx.x.x.x.x/conf/controller-info.xml'. It is also necessary to set the property such as <application-name>, <tier-name> and <node-name> which is described as "Required:Yes" in the following document. https://docs.appdynamics.com/display/PRO45/Java+Agent+Configuration+Properties#JavaAgentConfigurationProperties-Agent-ControllerCommunicationProperties 2. If you use a proxy, please set the information in your system property. https://docs.appdynamics.com/display/PRO45/Java+Agent+Configuration+Properties#JavaAgentConfigurationProperties-ProxyPropertiesfortheController 3. Please share the result of the command "nslookup <YOUR HOST NAME HERE>" in order to confirm that name resolution is working fine. ---<example>----- C:\Users\myaccount>nslookup mysaasaccount2020021717171312.saas.appdynamics.com Server: UnKnown Address: xxx.xx.xxx.xx Name: xxxxx.saas.appdynamics.com Addresses: xx.xx.xx.x xx.xx.xx.x Aliases: mysaasaccount.saas.appdynamics.com.localdomain ----------------- If you still have any problem, please copy a few lines of log file which has errors. (Log files cannot be attached because they are deleted for security and privacy reasons.) Best regards, Yusuke ... View more

Hi Tezuka-san, Thanks for reaching out to the community. We don’t restrict the number of local users as far as I know, but in case you are authenticating with LDAP, please be aware that LDAP servers can sometimes limit the number of entries returned in a query response. For more information, please see the document below. [URL] https://docs.appdynamics.com/display/PRO45/LDAP+Authentication [Section to be Helpful] "Configure the Connection to the LDAP Server" "Using Paged Results for Large Result Sets" Best regards, Yusuke ... View more

Hi Srikanth, Thanks for reaching out to the community. Regarding the message, as the agent is running as expected then you can ignore it now for the following reason. [Reason]------------------- For a JVM, there is a build-in classLoader java.lang.ClassLoader. The message indicated that there is no class loader with that name. However, JVM would run through the delegate chain of class loader to find the appropriate one during the startup. Ref: https://blogs.oracle.com/sundararajan/understanding-java-class-loading --------------------------------- If your node still doesn't show up on your controller, please file a help ticket in Zendesk with your logs for faster resolution of the issue. Best regards, Yusuke ... View more