• Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • Running Hudson in Master-Slave configuration on dedicated virtual windows servers. Servers have 4 CPUs with 1GB of memory allocated per CPU, with each slave and the master assigned to an individual CPU.

      Encountering problem with the Locks & Latches mechanism. When the jobs that block all other builds are running, blocked builds still occasionally post to an executor but don't build until the blocked builds finish. When this occurs, if Hudson picks up another change and fires off another build of the same project it queues it. However when the build blocking other builds finishes, the queued build goes and builds on a different executor before the original job request already farmed to an executor can start, and then the original job stays locked on that executor. Subsequent builds for that project will always queue and never build again while that executor stays offline even though it shows no activity (you can only see that a build is still on hold by going to the project and looking at build history where the faulty build is still building).

      Hudson master has to be restarted to reset and clear things, because nothing else works.

          [JENKINS-6901] Excecuter locks out build task

          njsf added a comment - - edited

          I also see this issue very frequently.

          In my case it is a very simple install of just one Hudson instance on a Linux RHEL5 box, local ext3 file systems.

          njsf added a comment - - edited I also see this issue very frequently. In my case it is a very simple install of just one Hudson instance on a Linux RHEL5 box, local ext3 file systems.

          Julien R. added a comment -

          if you don't want to restart jenkins, you could delete the stuck job, but yeah nothing seems to be able to kill it.
          Maybe a random (per job) quiet period could mitigate the issue.

          Julien R. added a comment - if you don't want to restart jenkins, you could delete the stuck job, but yeah nothing seems to be able to kill it. Maybe a random (per job) quiet period could mitigate the issue.

          Mark Waite added a comment -

          The Hudson locks and latches plugin is not distributed by the Jenkins update center. It was proposed for deprecation in 2015 and has known blocking issues. It prevents the saving of Jenkins job configurations in Jenkins 2.277.1 and later.

          If someone adopted the plugin, updated it to work with Jenkins 2.277.1 and later, and released a new version, then this issue report could be reopened.

          Mark Waite added a comment - The Hudson locks and latches plugin is not distributed by the Jenkins update center. It was proposed for deprecation in 2015 and has known blocking issues. It prevents the saving of Jenkins job configurations in Jenkins 2.277.1 and later. If someone adopted the plugin, updated it to work with Jenkins 2.277.1 and later, and released a new version, then this issue report could be reopened.

            Unassigned Unassigned
            alexlombardi alexlombardi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: