DocumentationJava Profiler Knowledge BaseTroubleshooting: working with the profiler'Connect to remote application' cannot find profiled application

Can't find your answer? Please refer to documentation and demos, ask your question in forum, or contact support.

• Ensure that the application is started with the profiler and is running when you connect.

  If it didn't start or terminated by the moment, check the application's output, logs etc. for possible errors, or restart the application if it was intentionally shut down.

• If the application is up and running, ensure that the network connection is not blocked by a firewall, an antivirus etc.

  Check both the remote machine side and the local machine side. The profiler agent port must be allowed. For detail on the used port please read description of 'port' option here.

  If the profiler agent port is not in the default range 10001-10010, explicitly specify the port in the connect dialog as host:port

  If you are unsure which port is used, look at the profiler agent log. It is created in <user home>/.yjp/log/<PID>.log, where <user home> corresponds to the account under which the profiled application is started.

  The log file location is also printed to stderr:
  [YourKit Java Profiler <version>] Loaded. Log file: <full path to the log file>

  Version 8.0.x and older agents used to print the port to stderr only:
  [YourKit Java Profiler 8.0.7] Profiler agent is listening on port 10001...