Could not initialize class hudson.model.Fingerprint
Jim McCaskey
Hello all,
I've been having a problem for a few weeks with my Maven builds. I'm not really certain where it started, but I have verified that it still happens on Jenkins build 1.423.
As you can see below, it appears that Fingerprinting is broken somehow. I'm guessing this is not hitting too many people. Any advice on how to track this down?
-Jim
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 59 seconds
[INFO] Finished at: Mon Aug 01 13:42:07 CDT 2011
[INFO] Final Memory: 64M/404M
[INFO] ------------------------------------------------------------------------
ERROR: Asynchronous execution failure
java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: Could not initialize class hudson.model.Fingerprint
at hudson.remoting.Channel$2.adapt(Channel.java:663)
at hudson.remoting.Channel$2.adapt(Channel.java:658)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:176)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:1027)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:958)
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:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class hudson.model.Fingerprint
at hudson.model.FingerprintMap.load(FingerprintMap.java:94)
at hudson.model.FingerprintMap.load(FingerprintMap.java:45)
at hudson.util.KeyedDataStorage.get(KeyedDataStorage.java:154)
at hudson.model.FingerprintMap.get(FingerprintMap.java:79)
at hudson.model.FingerprintMap.get(FingerprintMap.java:45)
at hudson.util.KeyedDataStorage.getOrCreate(KeyedDataStorage.java:108)
at hudson.model.FingerprintMap.getOrCreate(FingerprintMap.java:65)
at hudson.maven.reporters.MavenArtifact.recordFingerprint(MavenArtifact.java:280)
at hudson.maven.reporters.MavenArtifactRecord.recordFingerprints(MavenArtifactRecord.java:218)
at hudson.maven.reporters.MavenArtifactArchiver$2.call(MavenArtifactArchiver.java:142)
at hudson.maven.reporters.MavenArtifactArchiver$2.call(MavenArtifactArchiver.java:128)
at hudson.maven.MavenBuild$ProxyImpl.execute(MavenBuild.java:433)
at hudson.maven.MavenBuild$ProxyImpl2.execute(MavenBuild.java:506)
at sun.reflect.GeneratedMethodAccessor257.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at hudson.model.Executor$1.call(Executor.java:459)
at hudson.util.InterceptingProxy$1.invoke(InterceptingProxy.java:23)
at $Proxy32.execute(Unknown Source)
at hudson.maven.MavenBuildProxy$Filter$AsyncInvoker.call(MavenBuildProxy.java:263)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
... 6 more
Jim McCaskey
Hello all,
I have tried deleting the fingerprint directory (don't use them anyway) to see if that would clean this up, no luck. If it helps this is happening on a Windows 2003 slave, my Master does not run builds anymore.
It does not prevent Jenkins from working, but when a build breaks, it appears to still run this fingerprinting code. That means that when the system sends the build break notices all anyone sees are these fingerprinting errors.
Is there any way to debug this?
-Jim
Jim McCaskey
Hello all,
Well, I appear to be talking to myself here, but I thought I would share what the solution was.
Turns out a Jenkins update does not really update everything. When I tried debugging into the code, the line numbers from the stack trace where not lining up with what was in the remoting-2.4.jar. It turns out that I had remoting-2.1.jar sitting in my file system. I have no idea how that’s possible, but here is how I fixed it (this is on Windows 2003 R2).
1) Shutdown Jenkins service
2) rd /s/q <jinkins_install_dir>\war
3) Start Jenkins service
That caused Jenkins to reexpand the war and persto, remoting-2.4.jar appeared. Further testing showed that the Fingerprinting problem has gone away. I also notice about 5-6 other jars that where not updating.
Now, my Jenkins installation has been being updated since almost the first Jenkins release (after the Hudson split). So maybe something just got "stuck", but I found this to be pretty odd.
This was my solution to the problem. YMMV