Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why is the JRockit JVM throwing IllegalAccessError, ClassFormatError, IncompatibleClassChangeError or other LinkageError exceptions when the Sun JVM is not?

0
Posted

Why is the JRockit JVM throwing IllegalAccessError, ClassFormatError, IncompatibleClassChangeError or other LinkageError exceptions when the Sun JVM is not?

0

Verification ensures that the binary representation of a class or interface is structurally correct. For example, it checks that every instruction has a valid operation code; that every branch instruction branches to the start of some other instruction, rather than into the middle of an instruction; that every method is provided with a structurally correct signature; and that every instruction obeys the type discipline of the Java programming language. If an error occurs during verification, then a linkage error will be thrown at the point in the program that caused the class to be verified; for example: Using JTidy throws IllegalAccessError In an early version of JTidy from Apache Software Foundation, the compiler had incorrectly inlined a reference to a private variable belonging to an outer class. This caused an exception to be thrown since the JRockit JVM does stricter verification than the Sun JVM is. The old Tidy.jar should be replaced with the new and correctly compiled version.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123