multiple runs claiming to be #

Showing 1-3 of 3 messages
multiple runs claiming to be # Felix Köhler 9/26/12 4:32 AM
Hi erveryone,

Im new to this list. I tried serveral other communication way but found no good solution.

After i restarted my Server with my tomcat/jenkins installation i got a strange problem.
Every Job (if they are the same type - Free Job Configuration) they have the same Build History.

For example at job "Alice Project" the build number was 107 and an other job "Bob Project" with the highest build number 42 in the Build History.
After restarting, every Job has the same Build History. If i start a new build on "Bob Project", the new choosen build number is correct 43. But this number is not shown on the in the Build history because the highest number shown is #107 and so #43 will not displayed. The Alice and Bob Project are on the same git repository and it makes no difference if they are on different branches.

When i check the Tomcatlog i get serval warnings like:

WARNUNG: multiple runs claiming to be #0; using run from C:\Jenkins\builds\2012-09-26_10-55-40
26.09.2012 11:35:05 hudson.model.RunMap load
WARNUNG: multiple runs claiming to be #0; using run from C:\Jenkins\builds\2012-09-26_11-01-16
26.09.2012 11:35:05 hudson.model.RunMap load
WARNUNG: multiple runs claiming to be #0; using run from C:\Jenkins\builds\2012-09-26_11-01-17

Information:

  • Buildsystem: Jenkins 1.483 Win XP 32 bit Java 7
  • 5 Jobs on the same git-repsoitory
  • Building of an Eclipse application and an Andorid application with Maven


I have to add that i get an Error while stopping Tomcat but i think that they different problems.

...

[some more errors like the follow ones]

SCHWERWIEGEND: The web application [] created a ThreadLocal with key of type [org.apache.tools.ant.Project$1] (value [org.apache.tools.ant.Project$1@1cf3d]) and a value of type [java.lang.Boolean] (value [false]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
26.09.2012 10:47:52 org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SCHWERWIEGEND: The web application [] created a ThreadLocal with key of type [org.kohsuke.stapler.Stapler$1] (value [org.kohsuke.stapler.Stapler$1@18af3ef]) and a value of type [java.text.SimpleDateFormat] (value [java.text.SimpleDateFormat@c4dc9900]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
26.09.2012 10:47:52 org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SCHWERWIEGEND: The web application [] created a ThreadLocal with key of type [net.sf.json.AbstractJSON$1] (value [net.sf.json.AbstractJSON$1@194e11d]) and a value of type [java.util.HashSet] (value [[]]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
26.09.2012 10:47:52 org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks

...

And i have to kill the tomcat process.


Re: multiple runs claiming to be # cjo 9/26/12 5:44 AM
I saw a similar issue once when I miss configured an instance, when the builds directory was set the same for all projects.
 

From the paths to the builds you give, it seems like you have the same problem.

under the Manage Jenkins/configure page 
advanced section under home path.

check that the path to the builds directory has the $PROJECT_NAME (check the help for correct variable) specified in it somewhere.


The reason for this is that Jenkins uses the build folders (2012-09-26_11-01-17, etc) as referencs for the past builds, so having them all generated into the same root directory causes it to see all build results for every job. And if the OS supports links these are overridden by the job that last ran, causing links to be pointing to different builds than they should be.

Chris
Re: multiple runs claiming to be # Felix Köhler 9/26/12 6:27 AM
Thanks you made my day!

I changed the path to ${ITEM_ROOTDIR}/builds .