Discussion Feed

Yusuke.Miyahara · ‎01-06-2021

If someone faces the error below when encrypting, Caused by: java.lang.ClassNotFoundException: sun.misc.BASE64Encoder Please use JRE bundled with the machine agent.

Yusuke.Miyahara · ‎11-25-2020

After Java Agent installation, there is an “unable to identify hostname” error and the Controller can’t connect to Windows When installing Java Agent for Windows, there is an "unable to identify hostname" Error when telnet is checked to Controller connection. Diagnostics To troubleshoot the issue, start by reviewing the following: Can your DNS resolve the SaaS Controller host name? To confirm this, review the result of command: " nslookup <YOUR HOST NAME HERE> ". ---<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 the hostname successfully resolves, continue to step 2 of the diagnostics. Is your <controller-host> set in <agent_home>/verx.x.x.x.x/conf/controller-info.xml ? Be sure you have also set the property such as <application-name> , <tier-name> and <node-name> , to "Required:Yes" as described in the Java Agent Configuration Properties, Agent-Controller Communication Properties documentation. Do you use a proxy? If so, be sure to set the information in your system property as described in the Java Agent Configuration section of the Java Agent Configuration Properties documentation. Still experiencing a problem? Open a Support ticket where you’ll share the Agent log files—particularly the lines that show errors.

Yusuke.Miyahara · ‎02-20-2020

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

Yusuke.Miyahara · ‎02-19-2020

Hello Harrison, Thank you for reaching out to the community. We do not support for Linq query with lambda expression in data collector/information point getter chain. Apologies for the inconvenience. The workaround is to add the getter method that returns the evaluated value, and add data collector to this method. Please consult the following steps and the reference. (For example, it is assumed that getActionType and getResultMessage are implemented.) Steps: 1. Go Configuration > Instrumentation in your SaaS controller web page. 2. Click the Data Collector tab and click the Add button below the Method Invocation Data Collectors panel. 3. Input the following fields and click the save button. <Example> Name: MyDataCollector Class: with a class name that equals MyApplication.mynamespace.myclass Method Name: Mymethod Match Conditions: Collect Data From : Method Parameter @index:0 Operation on Method Parameter: Use Getter Chain: getActionType() Equals: Settle 4. Click the Add button below the Specify the Data to Collect from this Method Invocation panel. 5. Input the following fields and click the save button. <Example> Display Name: MyDataCollector Collect Data From : Method Parameter @index:0 Operation on Method Parameter: Use Getter Chain: getResultMessage() 6. Click the save button. 7. You must wait one minute and restart the CLR for the changes to take effect. Reference: https://docs.appdynamics.com/display/PRO45/Data+Collectors Best regards, Yusuke

Yusuke.Miyahara · ‎02-18-2020

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

Yusuke.Miyahara · ‎02-06-2020

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

Yusuke.Miyahara · ‎02-05-2020

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

Date Registered	‎01-23-2020 08:33 PM
Date Last Visited	‎09-17-2021 06:33 PM
Total Messages Posted	8
Total Kudos Received	9

Discussion Feed

Re: How do I use Password Encryption with Extensio...

DNS can’t ID Controller hostname when installing J...

Re: Agent nodes replicating themselves

Re: Lamda Expression in .NET Getter Chain

Re: "unable to identify hostname" when trying to i...

Re: Is there a limit on the number of local users ...

Re: I installed the IBM java agent, but getting th...