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.

Profiled application fails to start as Windows service

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

First, check that profiler agent is properly loaded.

Error messages can help troubleshooting the startup failure. Please check whether your server logs contain related errors. To find out where the console output is redirected to, check the server settings.

The profiler agent writes logs to file <user home>/.yjp/log/<session name>-<PID>.log instead of stderr.

Please note that Windows service is usually started under special user, thus the logs are located in that special user's home directory. For example, it can be C:\WINDOWS\system32\config\systemprofile.

If you have difficulties finding the log file directory, create the log in an arbitrary easily accessible directory instead, e.g. c:\logs, using the startup option logdir.

Some JEE servers can be configured to start with enabled debugger, by specifying VM options such as -Xdebug, -Xrunjdwp, -agentlib:jdwp. Due to limitations of current JVMs, a profiler agent needs to undertake special measures to successfully start alongside with debugger. The profiler agent inside a Windows service cannot automatically detect the debugger, thus a startup option withdebugger must be explicitly specified.