Fully featured low overhead profiler for Java EE and Java SE platforms.
Monitoring and profiling solution for Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

Remote profiling troubleshooting

If the profiler cannot connect to a remote application:

  • 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.

    The profiler agent port is not the same port as the ports which your profiled application normally uses, such as 8080 etc.

    The default profiler agent port range is 10001-10010. When an application starts with the profiler, the profiler first makes attempt to allocate a free port in this range. Remote profiled applications listening on ports in this range can be automatically detected when you connect.

    If all ports in the range are busy, an arbitrary port is chosen. In this case, you should explicitly specify the host and the port in the connect dialog as host:port You can find the port number on the remote machine in the log file <user home>\.ynp\log\<session name>-<PID>.log