Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    via Stack Overflow by ERJAN

    This exception occurs when using an older version of java. Mainly when trying to run a jar compiled with a newer Java version in an older Java version. We can avoid this issue by executing the jar in the same version which it was compiled.

  2. ,
    via Google Groups by Marcus Haebler

    Update "latest" to Java 8 on DockerHub.

Solutions on the web

via one-jar by sforge-kumar
, 1 year ago
Bad version number in .class file
via Google Groups by RickHigh, 2 years ago
Bad version number in .class file
via Oracle Community by 802550, 1 year ago
via Oracle Community by 843859, 10 months ago
Bad version number in .class file
via Stack Overflow by alex
, 2 years ago
Bad version number in .class file
via Google Groups by momalxa, 1 year ago
Bad version number in .class > file
Empty query.