Fully featured low overhead profiler for Java EE and Java SE platforms.
Performance monitoring and profiling of Jenkins, TeamCity, Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

Local profiling troubleshooting

If the profiler cannot connect to a local application:

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

    You cannot profile application started without the profiler. The only exception is applications running on .NET Framework 4 or newer, which support attaching of the profiler to an already running process. However, the attach mode has its limitations, thus you may prefer to start application with the profiler instead.

    If the application has not started or unexpectedly terminated, check the application's output and logs for possible errors. Please also check the profiler agent log file <user home>\.ynp\log\<session name>-<PID>.log

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

    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. 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 in the profiler agent log file <user home>\.ynp\log\<session name>-<PID>.log

  • Due to some system settings such as security permissions, enabling profiling may not work for some .NET applications.

    In this case, the application will start, but the profiler agent log file <user home>\.ynp\log\<session name>-<PID>.log will not be created.

    As a workaround, try to enable profiling manually.

  • If application to be profiled has started with the profiler, which is shown by the profiler agent log file which has been created (<user home>\.ynp\log\<session name>-<PID>.log), but the Welcome screen does not show the application, please try Profile remote application... action on Welcome screen, specifying "localhost" as host name, and using the port which you should have seen in the profiler agent log.