Skip to end of metadata
Go to start of metadata

Jenkins dedicates a java.lang.Thread for each executor. Under normal operation, this thread is alive all the time (although unless a build is going on the thread is sleeping.) The "dead executor" sign (see the picture on the right) happens when this thread dies unexpectedly. When this happens, please check your Jenkins system log (http://server/jenkins/log) and look for a stack trace, then report that to Jenkins users list or the issue tracker.

Obsolete as of Jenkins 2.13.

  • No labels


  1. The server had to be restarted in mid-build and now all the executioners are dead. How can I resolve this?

  2. im getting the dead alert on jenkins (site monitor job) it a bug frm site monitor plugin or jenkins...


    pls assist asap

  3. I   met one slave  dead always,but master and slave all dead, except slaves  which are  running jobs.If  need log,I can sutmit

    Sep 18, 2014 4:06:19 PM hudson.ExpressionFactory2$JexlExpression evaluate
    WARNING: Caught exception evaluating: item.isStuck() in /view/Z2_SISLEY/ajaxBuildQueue. Reason: java.lang.ArrayIndexOutOfBoundsException: Assertion error: fa
    iling to load #123 DESC: lo=18,hi=16,size=18,size2=18
    java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #123 DESC: lo=18,hi=16,size=18,size2=18
            at hudson.model.AbstractBuild.getPreviousBuild(
            at hudson.model.AbstractBuild.getPreviousBuild(
            at hudson.model.Job.getLastBuildsOverThreshold(
            at hudson.model.Job.getEstimatedDuration(
            at hudson.model.Queue$BuildableItem.isStuck(
            at sun.reflect.GeneratedMethodAccessor734.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(
            at java.lang.reflect.Method.invoke(
            at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(
            at org.apache.commons.jexl.parser.ASTMethod.execute(
            at org.apache.commons.jexl.parser.ASTReference.execute(
            at org.apache.commons.jexl.parser.ASTReference.value(
            at org.apache.commons.jexl.parser.ASTReferenceExpression.value(
            at org.apache.commons.jexl.ExpressionImpl.evaluate(
            at hudson.ExpressionFactory2$JexlExpression.evaluate(
            at org.apache.commons.jelly.tags.core.CoreTagLibrary$
            at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$
            at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$
            at org.apache.commons.jelly.TagSupport.invokeBody(
            at org.apache.commons.jelly.tags.core.ForEachTag.doTag(

  4. when the newest BUILD_ID is smaller than a builded one,this happens.
    java.lang.IllegalStateException: /usr1/home/jobs/CoreCD_Tool_V100R017C10_MR_Compile_RecordVisitor/builds/508 already existed; will not overwrite with CoreCD_Tool_V100R017C10_MR_Compile_RecordVisitor #508
    	at hudson.model.RunMap.put(
    	at jenkins.model.lazy.LazyBuildMixIn.newBuild(
    	at hudson.model.AbstractProject.newBuild(
    	at hudson.model.AbstractProject.createExecutable(
    	at hudson.model.AbstractProject.createExecutable(
    	at hudson.model.Executor$
    	at hudson.model.Executor$
    	at hudson.model.Queue._withLock(
    	at hudson.model.Queue.withLock(

    remove the builds history or set next build number bigger can solve it

    1. I am facing the same issue. There is also an option 'Restart the thread' showing up. This is freeing up the executor.

      My question is whether this is sufficient?


      1. Aditi, 'Restart the thread' will just clear it out.

        To fix this issue install 'Set Next Build Number' jenkins plugin.

        Give the next build number in jenkins job using this plugin.

        Refer "Next Build Number Plugin" for more information.