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

Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830

    Details

    • Similar Issues:
    • Released As:
      JFR 1.0-beta-12

      Description

      When using a Jetty version from the core (9.4.12.v20180830) on the current JFR master branch, I get the following error during the startup:

      2019-05-13 23:45:58.737+0000 [id=1] WARNING o.e.jetty.webapp.WebAppContext#doStart: Failed startup of context o.e.j.w.WebAppContext@7ef27d7f{Jenkins v2.164.2,/jenkins,file:///app/jenkins/,UNAVAILABLE}{/app/jenkins} java.lang.IllegalStateException: No config path set at org.eclipse.jetty.security.PropertyUserStore.loadUsers(PropertyUserStore.java:246) at org.eclipse.jetty.security.PropertyUserStore.doStart(PropertyUserStore.java:329) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.security.HashLoginService.doStart(HashLoginService.java:192) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.security.SecurityHandler.doStart(SecurityHandler.java:361) at org.eclipse.jetty.security.ConstraintSecurityHandler.doStart(ConstraintSecurityHandler.java:448) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:108) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:123) at org.eclipse.jetty.server.session.SessionHandler.doStart(SessionHandler.java:503) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:108) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:123) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:908) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:370) at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1497) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1459) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:847) at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:287) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:545) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138) at org.eclipse.jetty.server.Server.start(Server.java:416) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:108) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.server.Server.doStart(Server.java:383) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at io.jenkins.jenkinsfile.runner.JenkinsfileRunnerLauncher.createWebServer(JenkinsfileRunnerLauncher.java:62) at io.jenkins.jenkinsfile.runner.JenkinsEmbedder.newHudson(JenkinsEmbedder.java:317) at io.jenkins.jenkinsfile.runner.JenkinsEmbedder.before(JenkinsEmbedder.java:188) at io.jenkins.jenkinsfile.runner.JenkinsfileRunnerLauncher.before(JenkinsfileRunnerLauncher.java:87) at io.jenkins.jenkinsfile.runner.JenkinsfileRunnerLauncher.launch(JenkinsfileRunnerLauncher.java:124) at io.jenkins.jenkinsfile.runner.App.run(App.java:14) at io.jenkins.jenkinsfile.runner.bootstrap.Bootstrap.run(Bootstrap.java:206) at io.jenkins.jenkinsfile.runner.bootstrap.Bootstrap.main(Bootstrap.java:94)
      

      JFR run still finishes successfully, but this error is quite annoying. It looks to be somehow related to https://github.com/eclipse/jetty.project/issues/1602

      Acceptance criteria:

      • JFR does not print error on startup after the Jetty upgrade

        Attachments

          Activity

          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Jetty update is the root cause. It works well after reverting the JFR Jetty version to 9.4.5.v20170502

          Show
          oleg_nenashev Oleg Nenashev added a comment - Jetty update is the root cause. It works well after reverting the JFR Jetty version to 9.4.5.v20170502
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          I am reverting Jetty as a temporary workaround: https://github.com/jenkinsci/jenkinsfile-runner/pull/125

          Show
          oleg_nenashev Oleg Nenashev added a comment - I am reverting Jetty as a temporary workaround:  https://github.com/jenkinsci/jenkinsfile-runner/pull/125
          Hide
          alecharp Adrien Lecharpentier added a comment -

          Regression is fixed by reverting Jetty version. Fix is "just" a few days improvements.

          Show
          alecharp Adrien Lecharpentier added a comment - Regression is fixed by reverting Jetty version. Fix is "just" a few days improvements.
          Hide
          mezpahlan Mez Pahlan added a comment -

          Hi Oleg Nenashev can I double check something please. I'm running the demos from https://github.com/jenkinsci/jenkinsfile-runner/tree/master/demo and after building the vanilla docker image I get the errors in this issue. The sample pipeline runs fine but there's a lot of log noise at the start.

          The change in https://github.com/jenkinsci/jenkinsfile-runner/pull/177 seems to have reverted the workaround you've mentioned in https://github.com/jenkinsci/jenkinsfile-runner/pull/125. Was that to be expected?

          Great project btw, I'm really looking forward to using it in our production.

          Show
          mezpahlan Mez Pahlan added a comment - Hi Oleg Nenashev can I double check something please. I'm running the demos from https://github.com/jenkinsci/jenkinsfile-runner/tree/master/demo and after building the vanilla docker image I get the errors in this issue. The sample pipeline runs fine but there's a lot of log noise at the start. The change in https://github.com/jenkinsci/jenkinsfile-runner/pull/177 seems to have reverted the workaround you've mentioned in https://github.com/jenkinsci/jenkinsfile-runner/pull/125 . Was that to be expected? Great project btw, I'm really looking forward to using it in our production.
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Strange. New version worked for me on smoke tests. Will try it more and revert the version again if needed

          Show
          oleg_nenashev Oleg Nenashev added a comment - Strange. New version worked for me on smoke tests. Will try it more and revert the version again if needed
          Hide
          mezpahlan Mez Pahlan added a comment -

          I am a very new to Docker so please excuse me if I am doing something wrong but I was following the CWP demo and running the commands from the Makefile. I've ran the commands from buildInDocker: .copySource .buildInDocker .buildImage. Same error output at the very start but the pipeline did execute successfully after that. Am I doing something wrong?

          Show
          mezpahlan Mez Pahlan added a comment - I am a very new to Docker so please excuse me if I am doing something wrong but I was following the CWP demo and running the commands from the Makefile . I've ran the commands from buildInDocker: .copySource .buildInDocker .buildImage . Same error output at the very start but the pipeline did execute successfully after that. Am I doing something wrong?
          Show
          oleg_nenashev Oleg Nenashev added a comment - https://github.com/jenkinsci/jenkinsfile-runner/pull/281  for the fix
          Show
          oleg_nenashev Oleg Nenashev added a comment - https://github.com/jenkinsci/jenkinsfile-runner/releases/tag/1.0-beta-12

            People

            • Assignee:
              oleg_nenashev Oleg Nenashev
              Reporter:
              oleg_nenashev Oleg Nenashev
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: