Bad version number in .class file

[tori]

Hello,

we have Jenkins running on a *nix machine with 1.6 Java (64bit,
JRockit). We have a project, which has to use 1.5 Java and we set this
project with 1.5 Java (64 bit, Sun) as a JDK. Sometime between
versions 1.392 and 1.394 our build started to fail with error message:

Started by user ***
Building on master
Updating ***
At revision 7712
no change for ***
Found mavenVersion 2.2.1 from file jar:file:/opt/maven/apache-
maven-2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/
maven-core/pom.properties
Parsing POMs
[trunk] $ /usr/java/jdk1.5.0_22//bin/java -Xms256m -Xmx512m -cp /opt/
hudson_home/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.395.jar:/
opt/maven/apache-maven-2.2.1/boot/classworlds-1.1.jar
hudson.maven.agent.Main /opt/maven/apache-maven-2.2.1/ /opt/apache-
tomcat-7.0.6/webapps/hudson/WEB-INF/lib/remoting-1.396.jar /opt/
hudson_home/plugins/maven-plugin/WEB-INF/lib/maven-
interceptor-1.395.jar 52068 /opt/hudson_home/plugins/maven-plugin/WEB-
INF/lib/maven2.1-interceptor-1.2.jar
<===[HUDSON REMOTING CAPACITY]===>channel started
channel stopped
ERROR: Failed to parse POMs
java.io.IOException: Remote call on Channel to Maven [/usr/java/
jdk1.5.0_22//bin/java, -Xms256m, -Xmx512m, -cp, /opt/hudson_home/
plugins/maven-plugin/WEB-INF/lib/maven-agent-1.395.jar:/opt/maven/
apache-maven-2.2.1/boot/classworlds-1.1.jar, hudson.maven.agent.Main, /
opt/maven/apache-maven-2.2.1/, /opt/apache-tomcat-7.0.6/webapps/hudson/
WEB-INF/lib/remoting-1.396.jar, /opt/hudson_home/plugins/maven-plugin/
WEB-INF/lib/maven-interceptor-1.395.jar, 52068, /opt/hudson_home/
plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar] failed
at hudson.remoting.Channel.call(Channel.java:638)
at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:156)
at hudson.maven.MavenModuleSetBuild
$RunnerImpl.doRun(MavenModuleSetBuild.java:646)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:
420)
at hudson.model.Run.run(Run.java:1362)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:405)
at hudson.model.ResourceController.execute(ResourceController.java:
88)
at hudson.model.Executor.run(Executor.java:145)
Caused by: java.lang.UnsupportedClassVersionError: Bad version number
in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
at java.lang.ClassLoader.defineClass(ClassLoader.java:466)
at
hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:
151)
at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:
131)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at hudson.maven.MavenModuleSetBuild
$Builder.call(MavenModuleSetBuild.java:865)
at hudson.maven.MavenModuleSetBuild
$Builder.call(MavenModuleSetBuild.java:799)
at hudson.remoting.UserRequest.perform(UserRequest.java:114)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:
417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:595)
Finished: FAILURE

Some JUnit tests depend on 1.5 JDK, so we can't switch to default 1.6
JDK for this project, but when we tried switching - this error no
longer appeared, but tests failed.

Anyone has any ideas what could be wrong?

Thanks.

[Rainer Weinhold]

Got the same issue. Pretty sure this is a jenkins bug, Because it is working on the buildmachine without the jenkins agent stuff and jdk 1.5

Ticket :  http://issues.jenkins-ci.org/browse/JENKINS-8744

cheers Rainer

jenkins...@googlegroups.com schrieb am 04.02.2011 07:45:55:

> Von:
>
> tori <tori...@gmail.com>
>
> An:
>
> Jenkins Users <jenkins...@googlegroups.com>
>
> Datum:
>
> 04.02.2011 07:46
>
> Betreff:

>
> Bad version number in .class file

>
> Gesendet von:
>
> jenkins...@googlegroups.com

[Tomas Rimšelis]

Temporary solution for me: I run a secondary Tomcat server (this time 6.0.*) and newest Jenkins works fine there. More info [1].

1. http://issues.jenkins-ci.org/browse/JENKINS-8744?focusedCommentId=146123&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-146123