1. If an error message is returned indicating that the port 9996 is occupied, what can I do? You can modify the following configuration items in configuration files: collector.listen.port = 9996 in the collector/collector.config configuration file and profiler.collector.port = 9996 in the javaagent/javaagent.config configuration file.

  2. If an error message is returned indicating that JAVA_HOME cannot be found, what can I do? You can add JAVA_HOME to collector/run.sh and javaagent/attach.sh in Linux, or configure the path to JAVA_HOME in the startup command in Windows.

  3. The "com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: target process not responding or HotSpot VM not loaded" error is reported. What can I do? Ensure that you have granted the required permissions to the decompressed file. For more information, see the Deployment and collection topic in User Guide. If the agent is deployed independently, ensure that the account used to start the agent is the same as that used to start the application.

  4. How do I start the ADAM agent in Windows? The configurations of the ADAM agent are the same in Windows and Linux, except for the startup methods. You can use the Command Prompt to go to the collector directory and run the following command: start /b java -jar javaagent-collector.jar

     You can use the Command Prompt to go to the javaagent directory and run the following command:
     `java -cp "%JAVA_HOME%\lib\tools.jar;%cd%\javaagent-bootstrap.jar" com.alibaba.adam.javaagent.bootstrap.AgentAttacher -p %1`
    
     Note that you must replace $1 with the process ID of the container.
     If you want to start monitoring the application after restart, modify the corresponding bat file. For more information, see Method 2 described in the Deployment and collection topic in User Guide.
    
  5. What will happen if I restart the agent and collector? If you restart the collector, all collected data and cache will be cleared. You must decide whether to back up them before you restart the collector. If you restart the agent, new data will be combined with the existing data after deduplication.

  6. Is WebSphere supported? WebSphere that uses Sun or Oracle JDK 1.6 or later is supported. IBM JDK in WebSphere is not supported.

  7. Can I deploy multiple agents to monitor multiple applications? You can deploy an agent on a Java Virtual Machine (JVM) for monitoring purposes. If applications are deployed separately across multiple service containers, agents can also be deployed separately on the application regardless of how many machines the application is deployed on. However, an agent can monitor all applications that are deployed within the same service container because they are in the same JVM. In this case, you do not need to deploy multiple agents. Otherwise, an error will be reported, indicating that agents are duplicated.

  8. If an application is deployed on multiple servers, do I need to monitor and collect data from all the servers? If load balancing has been enabled for the application, you can monitor any two of the servers.

  9. Can I collect data from an application that uses JRE instead of JDK? Yes, but you must copy the tools.jar package from JDK to the ${JAVA_HOME}/lib/ directory.

  10. If I receive an agent already loaded error message from the standard output of the container after the agent is started, what can I do? A JVM cannot load the agent more than once. Therefore, you must restart the application, and then restart the agent by using Method 1 described in the Deployment and collection topic in User Guide.

  11. If I fail to start the agent and receive a Connection refused error message, what can I do? You can verify whether the process ID is valid.