ap-loader fails when trying to use the jfrsync command.

[egross]

The following error occurs while trying to use the --jfrsync option:

java -jar /home/location/ap-loader-all.jar profiler start -e cpu,alloc,wall --alloc 8m -j 128 --jfrsync default -d 600 -i 50ms -o jfr -f "/home/sfdc/maiev-shared/jfr/ap_dump_%n{2}.tmp" 487

[ERROR] Failed to initialize JfrSync class

When digging into the source, I am not seeing the helper directory from async-profiler in ap-loader

https://github.com/async-profiler/async-profiler/blob/master/src/helper/one/profiler/JfrSync.java

Was this missed during packaging ?

Thanks.

[parttimenerd]

Thanks for reporting this issue. I'll look into it tomorrow.

[parttimenerd]

You're correct, I never copied the files. Can you try it again with the files I just uploaded to the 4.2 release on GitHub?

[egross]

I'll have to test that version in another environment. The current testing environment uses maven to get the jar. I'll report back once I am able to do that.

[parttimenerd]

It seems to work for me at least. I'll release a proper new subversion once you can confirm that it's fixed.

[egross]

I can confirm it works now! Thank you!

[egross]

This is odd. I don't know what is up but I am not able to get jfrsync working again. It fails with the same error, even though I see the JfrSync class in the one/profiler directory. Any thoughts on how to debug it further?

[parttimenerd]

Not yet, I'll look into it next week.

[parttimenerd]

Maybe try calling java -jar /home/location/ap-loader-all.jar clear before?

[egross]

I don't know what is up but it is working today with new containers having spun up. Can you let me know where the temporary directory would be?

[parttimenerd]

java -jar /home/location/ap-loader-all.jar agentpath should give you a hint

[egross]

Perfect. Thanks a lot!