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

OpenText Application Automation Tools fail startup with Jenkins 2.459 and 2.460

XMLWordPrintable

      The Plugin throws an error when trying to install on a new Jenkins with version 2.460.
      We update our Jenkins weekly to avoid any security-issues etc. 

      The error breaks our build and we are not able to roll out new Jenkins-versions.

       

      Steps to repoduce:

      • run new Jenkins without plugins
      docker run --name jenkins --rm -p 8080:8080 docker.io/jenkins/jenkins:2.460-jdk17
      • try to install hp-application-automation-tools-plugin from Plugins-Screen

      Expected:

      • Plugin can be installed without any mayor issue

      Actual:

      • log shows an error (see attached log-file for complete stacktrace)
      Caused: com.google.inject.ProvisionException: Unable to provision, see the following errors:1) [Guice/ErrorInjectingConstructor]: NoClassDefFoundError: org/apache/commons/fileupload/FileItemFactory
  at GlobalEventsListenerOctaneImpl.<init>(GlobalEventsListenerOctaneImpl.java:62)Learn more:
  https://github.com/google/guice/wiki/ERROR_INJECTING_CONSTRUCTOR1 error======================
Full classname legend:
======================
GlobalEventsListenerOctaneImpl: "com.microfocus.application.automation.tools.octane.events.GlobalEventsListenerOctaneImpl"
========================
End of classname legend:
========================        at com.google.inject.internal.InternalProvisionException.toProvisionException(InternalProvisionException.java:251)
        at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:43)
        at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:169)
        at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:448)
        at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:45)
        at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1148)
        at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:406)
        at hudson.ExtensionFinder$GuiceFinder$3.find(ExtensionFinder.java:360)
        at jenkins.ExtensionComponentSet$3.find(ExtensionComponentSet.java:98)
        at jenkins.ExtensionComponentSet$1.find(ExtensionComponentSet.java:70)
        at jenkins.ExtensionComponentSet$3.find(ExtensionComponentSet.java:98)
        at jenkins.ExtensionComponentSet$3.find(ExtensionComponentSet.java:98)
        at hudson.ExtensionList.load(ExtensionList.java:391)
        at hudson.ExtensionList.refresh(ExtensionList.java:345)
        at jenkins.model.Jenkins.refreshExtensions(Jenkins.java:2934)
        at hudson.PluginManager.start(PluginManager.java:999)
        at hudson.model.UpdateCenter$CompleteBatchJob.run(UpdateCenter.java:2369)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
        at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:121)
        at java.base/java.lang.Thread.run(Unknown Source)

      After this, a configuration (e.g. Octane-Servers) is not possible.

       

        1. opentext-plugin-issue.log
          493 kB

          [JENKINS-73235] OpenText Application Automation Tools fail startup with Jenkins 2.459 and 2.460

          Daniel Horn created issue -

          Mark Waite added a comment -

          The issue may be related to JENKINS-72498 . That issue reports the plugin binary file includes many more dependencies than it needs to include.

          Mark Waite added a comment - The issue may be related to JENKINS-72498 . That issue reports the plugin binary file includes many more dependencies than it needs to include.
          Mark Waite made changes -
          Summary Original: Unable to run OpenText Application Automation Tools with Jenkin 2.460 New: OpenText Application Automation Tools fail startup with Jenkins 2.459 and 2.460

          Mark Waite added a comment -

          I confirmed that the failure happens in 2.459 and 2.460 and does not happen in 2.458. I assume that the incorrect dependencies that are being included in the plugin will need to be fixed. JENKINS-72498 is the issue that tracks that fix

          Mark Waite added a comment - I confirmed that the failure happens in 2.459 and 2.460 and does not happen in 2.458. I assume that the incorrect dependencies that are being included in the plugin will need to be fixed. JENKINS-72498 is the issue that tracks that fix

          marco added a comment - - edited

          Do you have a hot fix for it ?, i need to have the latest Jenkins version and this issue might take a long time to fix?

          marco added a comment - - edited Do you have a hot fix for it ?, i need to have the latest Jenkins version and this issue might take a long time to fix?

          Mark Waite added a comment -

          I do not have a hot fix for it. The plugin maintainer will need to make the fix. Since application automation tools is a commercial product, you should use your support processes to request a fix from the commercial vendor.

          Mark Waite added a comment - I do not have a hot fix for it. The plugin maintainer will need to make the fix. Since application automation tools is a commercial product, you should use your support processes to request a fix from the commercial vendor.

          Daniel Horn added a comment - - edited

          We created a support request at the vendors portal
          https://portal.microfocus.com/s/customdetailpage?500Q4000008dyqwIAA=&language=en_US

           

          Thanks markewaite for the information. I assumed, the vendor also trackts this issue board.

          Daniel Horn added a comment - - edited We created a support request at the vendors portal https://portal.microfocus.com/s/customdetailpage?500Q4000008dyqwIAA=&language=en_US   Thanks markewaite for the information. I assumed, the vendor also trackts this issue board.

          Igor Kolomiyets added a comment -

          It seems that 2.459 introduced commons-fileupload2-core-2.0.0-M2.jar and commons-fileupload2-javax-2.0.0-M2.jar instead of commons-fileupload-1.5.jar which was used up to version 2.458 which breaks the plugin.

          The workaround is to copy commons-fileupload-1.5.jar file into plugins `WEB-INF/lib` directory `plugins/hp-application-automation-tools-plugin/WEB-INF/lib`.

          Igor Kolomiyets added a comment - It seems that 2.459 introduced commons-fileupload2-core-2.0.0-M2.jar and commons-fileupload2-javax-2.0.0-M2.jar instead of commons-fileupload-1.5.jar which was used up to version 2.458 which breaks the plugin. The workaround is to copy commons-fileupload-1.5.jar file into plugins `WEB-INF/lib` directory `plugins/hp-application-automation-tools-plugin/WEB-INF/lib`.

          Mark Waite added a comment - - edited

          Thanks for finding a workaround ikolomiyets, that's very good to share with others.

          The switch to Commons File Upload 2.x is part of the transition to upgrade from Spring Security 5.x to Spring Security 6.x. The Spring project has announced that August 31, 2024 is the end of life of Spring Security 5.x.

          Upgrading to Spring Security 6.x requires that we upgrade to Commons File Upload 2.x, Jetty 12, and Jakarta EE 9. Each of those upgrades is a major upgrade. The upgrade to Spring Security 6.x requires Java 17. That is coming soon to Jenkins weekly as well.

          The plugin maintainer needs to fix the excessive inclusion of dependencies in the plugin so that the workaround is not needed. That is described in JENKINS-72498

          Mark Waite added a comment - - edited Thanks for finding a workaround ikolomiyets , that's very good to share with others. The switch to Commons File Upload 2.x is part of the transition to upgrade from Spring Security 5.x to Spring Security 6.x. The Spring project has announced that August 31, 2024 is the end of life of Spring Security 5.x . Upgrading to Spring Security 6.x requires that we upgrade to Commons File Upload 2.x, Jetty 12, and Jakarta EE 9. Each of those upgrades is a major upgrade. The upgrade to Spring Security 6.x requires Java 17. That is coming soon to Jenkins weekly as well. The plugin maintainer needs to fix the excessive inclusion of dependencies in the plugin so that the workaround is not needed. That is described in JENKINS-72498

          Daniel Horn added a comment -

          Thank you all, for your continuous support.
          I relayed the information back to the maintainer/vendor.

          Daniel Horn added a comment - Thank you all, for your continuous support. I relayed the information back to the maintainer/vendor.

            buzas Laura Buzas
            dhorn Daniel Horn
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: