Redefinition failed with error 62 while trying to profile an application

Question

If I try to profile application, (which is prepared under Eclipse, but running from command line) with the help of VisualVM, I get the following error message

enter image description here

Simultaneously, the project folder is fouled with newly created class files. Although they are already existing in target/classes.

The project structure is Maven's, i.e. there is a foder target/classes in current directory and I us the following command to run the application

java -Xmx16g -cp target/classes tests.Runner01

How to fix?

UPDATE

The same occurs with conventional java project too.

Below it the picture of populated class files, which located where they should not

enter image description here

score 89 · Answer 1 · answered Nov 10 '14 at 19:14

89

Here https://netbeans.org/bugzilla/show_bug.cgi?id=191297 appears a workaround: run profiled application with -Xverify:none

answered Nov 10 '14 at 19:14

rafalopez79

2,046
4
27
23

2

The correct bug is this one: https://netbeans.org/bugzilla/show_bug.cgi?id=245522 and https://bugs.openjdk.java.net/browse/JDK-8050485. The problem is already fixed in JDK 7u71 and JDK 8u31. – Tomas Hurka Nov 12 '14 at 08:12
35

I ran into this problem with java version "1.8.0_121" – ezzadeen Mar 08 '17 at 18:37
@ezzadeen You solved this problem? I am also getting same. – Pritesh Kanthaliya Apr 06 '17 at 06:44
12

Problem still exists in 1.8.0_131 – Brian Knoblauch Jul 07 '17 at 15:10
and with 1.8.0_144 – 62mkv Nov 17 '17 at 09:41
and in 1.8.0_152 – Hummeling Engineering BV Jan 19 '18 at 10:37
7

still in 1.8.0_162, to put a bit salt – benez Feb 06 '18 at 17:53
I also encountered this bug, but upgrading to the latest version fixed the issue. – Henrique de Sousa Mar 26 '18 at 14:53
When I added `-Xverify:none`, the profiling tab didn't appear the next time I launched. – TMN Apr 24 '18 at 14:14
The bug is still present in 1.8.0_181. It disappeared with the suggested solution: -Xverify:none – stuhpa Sep 10 '18 at 13:55
Also had to use this workarround on JDK 11 in intellij – Wesley De Keirsmaeker Aug 25 '21 at 10:10
Same problem with 1.8.0_301 – DAB Aug 04 '22 at 09:06

score 9 · Answer 2 · answered Jun 25 '19 at 14:43

If you are using eclipse, then go to Run/Debug configuration. Select your application from left side and click on Arguments.

Here you will see two text boxes.

1. Program Arguments
2. VM Arguments

In VM arguments, enter below commands. -Xverify:none

Click on apply and then Run/Debug.

score 7 · Answer 3 · edited Feb 06 '19 at 08:37

7

According to this GitHub issue, it's been fixed. Updating to version 1.4 solved the problem for me.

edited Feb 06 '19 at 08:37

Tomas Hurka

6,723
29
38

answered Feb 07 '18 at 23:43

shmosel

49,289
6
73
138

Thanks for pointing this out. Ran into this problem today and updated VisualVM. It works now. – Torsten Ojaperv Feb 08 '18 at 13:03

score 2 · Answer 4 · answered Apr 14 '22 at 11:19

2

For IntelliJ, you can set -Xverify:none as follows:

Run > Edit Configurations... > Modify options (Alt + M) > Add VM options.

This should reveal a new field VM options, to which you can write -Xverify:none.

answered Apr 14 '22 at 11:19

Spacha

313
4
7

score 1 · Answer 5 · answered Nov 06 '17 at 20:13

1

The workaround I found using IntelliJ is to compile to Java 1.6 byte code. The menu option to do so is: File - Project Structure, then set Project language level to 6.

This precludes you from using Java features only available with Java 7 or 8.

answered Nov 06 '17 at 20:13

Stuart Hansen

21
1

score 0 · Answer 6 · answered Mar 15 '23 at 12:23

0

Just letting others know, adding the VM option -Xverify:none is the recommended way as per the official Troubleshooting Guide.

answered Mar 15 '23 at 12:23

Yuri

4,254
1
29
46

Redefinition failed with error 62 while trying to profile an application

6 Answers6

Linked