Java 11 support

[Anton Katilin]

Please don't forget that YourKit license offers 1 year of free upgrades, and that it never expires unlike a subscription based licensing very popular with other vendors nowadays. Everyone who purchased the license or renewed it less than a year before the release upgrade for free.

[grogozinsky]

I have upgraded to a new major version supporting JDK11 and now I have major problems.
First, when I add YKJ agent on server startup it doesn't seem to work. I don't see my application under "Connection" section. When I click on my application name under "Local Applications" section it appears under "Connection" with after a small delay, but I the CPU time shown when I start CPU Profiling with default sampling option is completely off (significanly smaller than a real time) and when I start CPU Profiling with tracing option time most of time it takes forever and I get an error that tracing is not available or some time it comes and time is significantly higher and most of time taken is shown from Logger.info.
With all of it the profiling is pretty much pointless for me. Previous version work much better.
Do you have any suggestions?
Here is how I start the profiler:
mvn spring-boot:run -Dspring-boot.run.jvmArguments="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005 -agentpath:C:\ProgramData\YourKit\2019.1.110.04084DAD\64\yjpagent.dll=disablestacktelemetry,exceptions=disable,delay=10000

[Anton Katilin]

Could you please send the profiler agent log file to [email protected]

[Anton Katilin]

I don't see my application under "Connection" section. When I click on my application name under "Local Applications" section it appears under "Connection" with after a small delay,

Is your application local or remote? If it's local, why do you expect to see it in remote connections?

but I the CPU time shown when I start CPU Profiling with default sampling option is completely off (significanly smaller than a real time)

Please try to add the line
-Dyjp.zero.time.methods=false
to <user home>/.yjp/ui.ini
If this doesn't help please provide a snapshot file demonstrating the problem.

and when I start CPU Profiling with tracing option time most of time it takes forever

Do you mean it takes forever to start CPU tracing (do you see a progress saying the classes are being retransformed?) or is the profiled application extremely slow with it?

and I get an error that tracing is not available

Could you please provide the exact error message.

or some time it comes and time is significantly higher and most of time taken is shown from Logger.info.

CPU tracing overhead may be significant, it's expected.

With all of it the profiling is pretty much pointless for me. Previous version work much better.

What previous version do you mean?

Here is how I start the profiler:
mvn spring-boot:run -Dspring-boot.run.jvmArguments="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005 -agentpath:C:\ProgramData\YourKit\2019.1.110.04084DAD\64\yjpagent.dll=disablestacktelemetry,exceptions=disable,delay=10000

Please note you enable debugger at the same time. Please check whether running without debugger makes a difference.

[grogozinsky]

Below are my answers inline in BOLD.
I don't see my application under "Connection" section. When I click on my application name under "Local Applications" section it appears under "Connection" after a small delay,
Is your application local or remote? If it's local, why do you expect to see it in remote connections?

My application is using spring-boot with embedded jetty container and YKJ agent is passed in JVM arguments and is remote, but in this particular case I was starting it on my local machine.

but the CPU time shown when I start CPU Profiling with default sampling option is completely off (significanly smaller than a real time)

Please try to add the line
-Dyjp.zero.time.methods=false
to <user home>/.yjp/ui.ini

Actually, I upgraded yesterday to build 111 and timing with sampling is much closer to the real one.

If this doesn't help please provide a snapshot file demonstrating the problem.
and when I start CPU Profiling with tracing option time most of time it takes forever

Do you mean it takes forever to start CPU tracing (do you see a progress saying the classes are being retransformed?) or is the profiled application extremely slow with it?
and I get an error that tracing is not available
Could you please provide the exact error message.
It takes forever to start CPU tracing and a lot of time it failes. I will provide a message next time it happens.

or some time it comes and time is significantly higher and most of time taken is shown from Logger.info.
CPU tracing overhead may be significant, it's expected.
With all of it the profiling is pretty much pointless for me. Previous version work much better.
What previous version do you mean?

The last early access build (I think it was 2018.5.90) worked much better in all aspects.

Here is how I start the profiler:
mvn spring-boot:run -Dspring-boot.run.jvmArguments="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005 -agentpath:C:\ProgramData\YourKit\2019.1.110.04084DAD\64\yjpagent.dll=disablestacktelemetry,exceptions=disable,delay=10000
Please note you enable debugger at the same time. Please check whether running without debugger

[Anton Katilin]

It takes forever to start CPU tracing and a lot of time it failes. I will provide a message next time it happens.

Yes, please. We'll also need the log file(s).

The last early access build (I think it was 2018.5.90) worked much better in all aspects.

"In all aspects" is too broad. We can investigate only particular issues.

Please provide all necessary detail on each issue you experience: log files, screenshot of errors, etc. Otherwise we cannot help.

[sandreev]

Just to double check whether this is expected:

YourKit Java Profiler 2019.8-b141 cannot run on Java 11.0.8, it requires Java 8.
(Note: this applies only to running YourKit Java Profiler itself. Your applications may run on Java 7 or newer.)

In this thread, statements are made in 2018, that an early access build fixes the problem? What build would that be, if the fix is not included in a 2019.8 release?

[Anton Katilin]

The current version 2020.7 runs on Java 11 itself and allows profiling of Java versions from Java 7 to Java 14.