Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to run jar on Amazon JVM #155

Open
spark85 opened this issue Sep 26, 2023 · 1 comment
Open

Unable to run jar on Amazon JVM #155

spark85 opened this issue Sep 26, 2023 · 1 comment
Labels

Comments

@spark85
Copy link

spark85 commented Sep 26, 2023

Jenkins and plugins versions report

Environment
Paste the output here

What Operating System are you using (both controller, and any agents involved in the problem)?

Mac Os Ventura 13.5.2, Java JVM Amazon Corretto 17 & 20. (Tried with multiple sub-releases)

Reproduction steps

  1. Setup the Amazon Corretto JVM as java home and set it on your zsh path.
  2. setup an Android gradle build (this is optional as it is unrelated to the bug. Just providing for context)
  3. Use the jar command to start the listener.
    java -jar {path-to-jar}file-leak-detector-1.16-jar-with-dependencies.jar PID http=19999

Expected Results

Command should execute successfully

Actual Results

The command does not complete and returns with the following error

com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize at jdk.attach/sun.tools.attach.HotSpotVirtualMachine.loadAgent(HotSpotVirtualMachine.java:170) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) at java.base/java.lang.reflect.Method.invoke(Method.java:580) at org.kohsuke.file_leak_detector.Main.run(Main.java:74) at org.kohsuke.file_leak_detector.Main.main(Main.java:38)

Anything else?

We can only use Amazon Corretto, it seems many other JVM's work including Bell & SAP

@spark85 spark85 added the bug label Sep 26, 2023
@Rodrigolmti
Copy link

Rodrigolmti commented Sep 27, 2023

I was having this issue, and figure out that I was not using the latest version. Check if you are using the 1.13, the latest is 1.16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants