Details

    • Similar Issues:

      Description

      The system started hanging without any change known to the system. Users always reported that Jenkins was sometimes slow, but I guess now it passed that threshold.

      I'm fairly new to thread dump and heap dump analysis, but from what I've see there is a bottle neck somewhere.

      • Garbage collection looks ok
      • System and JVM resources seem are not exceeded.

      I'm attaching the system info and a thread dumps from various freezes. Please let me know what else should I add. For some reason the /manage page doesn't want to load

        Attachments

          Issue Links

            Activity

            Hide
            danielbeck Daniel Beck added a comment -

            Thread Dump basics (and I really hope I'm right with a comment like this ):

            • Look for "BLOCKED" threads
            • Lock for what object they're blocked on (in this case 4eafeafb)
            • Look for the one thread that owns it (in this case Executor #1 for AMT2-slave)
            • Look at what it does (in this case hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.canTake)
            Show
            danielbeck Daniel Beck added a comment - Thread Dump basics (and I really hope I'm right with a comment like this ): Look for "BLOCKED" threads Lock for what object they're blocked on (in this case 4eafeafb ) Look for the one thread that owns it (in this case Executor #1 for AMT2-slave ) Look at what it does (in this case hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.canTake )
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            1.609.x release should have been solved the problem with UI hanging. That release introduced the asynchronous queue. In addition, UI has caching of queue items. So I would not expect TCB plugin to cause hanging in 1.532.

            BTW it needs an investigation

            Show
            oleg_nenashev Oleg Nenashev added a comment - 1.609.x release should have been solved the problem with UI hanging. That release introduced the asynchronous queue. In addition, UI has caching of queue items. So I would not expect TCB plugin to cause hanging in 1.532. BTW it needs an investigation
            Hide
            danielbeck Daniel Beck added a comment -

            Wait, what?

            Jenkins 1.532

            Is this a typo, or is the instance 100+ versions behind?

            Show
            danielbeck Daniel Beck added a comment - Wait, what? Jenkins 1.532 Is this a typo, or is the instance 100+ versions behind?
            Hide
            danielbeck Daniel Beck added a comment -

            Not a typo, runs Java 6.

            Oleg Nenashev Do you still care about that version for the plugin? From a core POV I don't, too old.

            Show
            danielbeck Daniel Beck added a comment - Not a typo, runs Java 6. Oleg Nenashev Do you still care about that version for the plugin? From a core POV I don't, too old.
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            I suspect it was my mistake. I've thought that the bug is for 1.632...
            For 1.532 the situation is pretty obvious - such delays happen. The best recommendation would be update the core. We made several attempts to solve the performance issue as a part of JENKINS-27650, but we didn't manage to improve it enough.

            Show
            oleg_nenashev Oleg Nenashev added a comment - I suspect it was my mistake. I've thought that the bug is for 1.632... For 1.532 the situation is pretty obvious - such delays happen. The best recommendation would be update the core. We made several attempts to solve the performance issue as a part of JENKINS-27650 , but we didn't manage to improve it enough.
            Hide
            silviump Silviu Marchis added a comment -

            1.532.2 more specifically. Yes the system is fairly behind, mostly because it was critical that the system was stable, so no one tinkered with it. But now there is this problem and we are strongly considering upgrading to a newer LTS

            Show
            silviump Silviu Marchis added a comment - 1.532.2 more specifically. Yes the system is fairly behind, mostly because it was critical that the system was stable, so no one tinkered with it. But now there is this problem and we are strongly considering upgrading to a newer LTS
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Nothing to do here, I'd say. Please reopen if it still happens on newer Jenkins versions

            Show
            oleg_nenashev Oleg Nenashev added a comment - Nothing to do here, I'd say. Please reopen if it still happens on newer Jenkins versions

              People

              • Assignee:
                oleg_nenashev Oleg Nenashev
                Reporter:
                silviump Silviu Marchis
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: