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

Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • crowd-plugin
    • None
    • jenkins from version 1.502
      crowd 1.3-SNAPSHOT

      As described here: http://jenkins.361315.n4.nabble.com/Getting-NoSuchClassDefFoundError-for-ehcache-td391329.html, the spring-context-support JAR that is now (from version 1.502 on) packaged into the jenkins.war is loaded instead of the one from crowd/WEB-INF/lib. So it does not find classes from the ehcache JAR packaged only in the crowd/WEB-INF/lib.

      (see attached jenkins.log for complete stack trace)

      Two possible solutions:

      1. remove the spring-context-support JAR from jenkins.war/WEB-INF/lib
      2. switch class loader lookup order to search "plugin/WEB-INF/lib" first (this way it would be possible for plugin developers to override JARs delivered with the jenkins core)

      This issue prevents me from using the newest jenkins versions (starting from 1.502).

        1. jenkins.log
          84 kB
        2. jenkins1.log
          14 kB

          [JENKINS-17288] Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly

          C2PA IT added a comment -

          Anyone know if this is going to be fixed by chance or if we just need to plan on implementing the workarounds in the future?

          C2PA IT added a comment - Anyone know if this is going to be fixed by chance or if we just need to plan on implementing the workarounds in the future?

          Marc Günther added a comment -

          Still not fixed in Jenkins LTS 1.532.2 and Crowd Plugin 1.2

          This essentially means that we cannot even upgrade to LTS. We are on 1.501 currently...

          Marc Günther added a comment - Still not fixed in Jenkins LTS 1.532.2 and Crowd Plugin 1.2 This essentially means that we cannot even upgrade to LTS. We are on 1.501 currently...

          Clément Billiot added a comment -

          Same issue for us, we are stuck with version 1.498

          Clément Billiot added a comment - Same issue for us, we are stuck with version 1.498

          Marc Günther added a comment -

          And Crowd2-Plugin has severe perfomance issues (we tried it), so it's not an option either: JENKINS-16703

          Marc Günther added a comment - And Crowd2-Plugin has severe perfomance issues (we tried it), so it's not an option either: JENKINS-16703

          Clément Billiot added a comment -

          You should use jenkins with tomcat and not with the embedded jetty, it has worked for us.

          Clément Billiot added a comment - You should use jenkins with tomcat and not with the embedded jetty, it has worked for us.

          Marc Günther added a comment -

          We use the standalone jar with embedded winstone, and it works when we delete the spring-context-support-2.5.6.SEC03.jar from the jenkins.war.

          Marc Günther added a comment - We use the standalone jar with embedded winstone, and it works when we delete the spring-context-support-2.5.6.SEC03.jar from the jenkins.war .

          Daniel Beck added a comment -

          Can't the Crowd plugin just switch to using the plugin first classloader?

          http://javadoc.jenkins-ci.org/hudson/PluginFirstClassLoader.html

          Daniel Beck added a comment - Can't the Crowd plugin just switch to using the plugin first classloader? http://javadoc.jenkins-ci.org/hudson/PluginFirstClassLoader.html

          Daniel Beck added a comment -

          Removing core component. Issues like these are what PluginFirstClassloader is designed for, and if not using that, it's no surprise this breaks.

          Daniel Beck added a comment - Removing core component. Issues like these are what PluginFirstClassloader is designed for, and if not using that, it's no surprise this breaks.

          Marc Günther added a comment -

          Any news on this one? We still have to remove that spring-context jar file manually, every time we do an upgrade of Jenkins...

          Marc Günther added a comment - Any news on this one? We still have to remove that spring-context jar file manually, every time we do an upgrade of Jenkins...

          C2PA IT added a comment -

          Still an issue for us as well.

          C2PA IT added a comment - Still an issue for us as well.

            rmangi rmangi
            rzanner René Zanner
            Votes:
            6 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: