Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-36115

java.util.ConcurrentModificationException when tried to open Jenkins via local host

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
    • Environment:
    • Similar Issues:

      Description

      Opening url http://localhost:8080 throwing below error,

      hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.util.ConcurrentModificationException
      at hudson.WebAppMain$3.run(WebAppMain.java:244)
      Caused by: org.jvnet.hudson.reactor.ReactorException: java.util.ConcurrentModificationException
      at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269)
      at jenkins.InitReactorRunner.run(InitReactorRunner.java:45)
      at jenkins.model.Jenkins.executeReactor(Jenkins.java:1010)
      at jenkins.model.Jenkins.<init>(Jenkins.java:878)
      at hudson.model.Hudson.<init>(Hudson.java:85)
      at hudson.model.Hudson.<init>(Hudson.java:81)
      at hudson.WebAppMain$3.run(WebAppMain.java:227)
      Caused by: java.util.ConcurrentModificationException
      at java.util.ArrayList$Itr.checkForComodification(Unknown Source)
      at java.util.ArrayList$Itr.next(Unknown Source)
      at hudson.PluginManager.resolveDependantPlugins(PluginManager.java:882)
      at hudson.PluginManager$2$2.run(PluginManager.java:563)
      at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
      at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
      at jenkins.model.Jenkins$7.runTask(Jenkins.java:999)
      at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
      at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)

        Attachments

          Issue Links

            Activity

            Hide
            markewaite Mark Waite added a comment -

            Lakshmi Brunda could you explain further why you think this stack trace is related to the git plugin or the github pull request builder plugin? The stack trace makes no reference to either of those plugins, nor does any error message point to either of those plugins.

            Show
            markewaite Mark Waite added a comment - Lakshmi Brunda could you explain further why you think this stack trace is related to the git plugin or the github pull request builder plugin? The stack trace makes no reference to either of those plugins, nor does any error message point to either of those plugins.
            Hide
            lbrunda Lakshmi Brunda added a comment -

            i have mentioned it under environment but not in the sense that error is because of those plugins.It was working fine till end of the day.But next day i tried to open jenkins freshly i faced Index out of bound exception then i stopped java SE binary and deleted Cloud bees folder and cloud bees plugin then it turned to above attached exception.

            Show
            lbrunda Lakshmi Brunda added a comment - i have mentioned it under environment but not in the sense that error is because of those plugins.It was working fine till end of the day.But next day i tried to open jenkins freshly i faced Index out of bound exception then i stopped java SE binary and deleted Cloud bees folder and cloud bees plugin then it turned to above attached exception.
            Hide
            markewaite Mark Waite added a comment -

            Thanks for the clarification. It sounds like you made a configuration change to an unrelated plugin and now need to revert that plugin. This bug either needs to be assigned to one of the projects that could do something about it, or closed so that you can shift the discussion about your configuration change to the Jenkins users mailing list.

            The bug database is not a good place for configuration change related questions because it is reviewed by far fewer people than the people who watch the Jenkins users mailing list.

            Show
            markewaite Mark Waite added a comment - Thanks for the clarification. It sounds like you made a configuration change to an unrelated plugin and now need to revert that plugin. This bug either needs to be assigned to one of the projects that could do something about it, or closed so that you can shift the discussion about your configuration change to the Jenkins users mailing list. The bug database is not a good place for configuration change related questions because it is reviewed by far fewer people than the people who watch the Jenkins users mailing list.
            Hide
            integer Kanstantsin Shautsou added a comment -

            No idea what right component is and there is no zero components, so to core.

            Show
            integer Kanstantsin Shautsou added a comment - No idea what right component is and there is no zero components, so to core.
            Hide
            hestersco Christophe Hesters added a comment -

            I just ran into this problem as well. I tried to update some plugins, but that failed due to a proxy exception. Then Jenkins was rebooted and shows exactly the same error. I can't find a solution.

            Show
            hestersco Christophe Hesters added a comment - I just ran into this problem as well. I tried to update some plugins, but that failed due to a proxy exception. Then Jenkins was rebooted and shows exactly the same error. I can't find a solution.
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            This is the issue in the core. From what I see after the quick look, it is still actual (maybe not)

            Show
            oleg_nenashev Oleg Nenashev added a comment - This is the issue in the core. From what I see after the quick look, it is still actual (maybe not)
            Hide
            liketic Li Ke added a comment -

            Is this bug still exists? I'm not sure if change 

            protected final List<PluginWrapper> plugins = new ArrayList<PluginWrapper>();
            

            to 

            protected final List<PluginWrapper> plugins = Collections.synchronizedList(new ArrayList<PluginWrapper());
            

            will work. 

            Show
            liketic Li Ke added a comment - Is this bug still exists? I'm not sure if change  protected final List<PluginWrapper> plugins = new ArrayList<PluginWrapper>(); to  protected final List<PluginWrapper> plugins = Collections.synchronizedList( new ArrayList<PluginWrapper()); will work. 

              People

              • Assignee:
                Unassigned
                Reporter:
                lbrunda Lakshmi Brunda
              • Votes:
                1 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated: