• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • None

      Hello, I'm having an issue deploying an EAR file to WebSphere and I think it's related to the JDK.

       

      Running the Jenkins service under the IBM JDK 6 results in a StackOverflowError and crashing of the Jenkins service:

      ...
      Connecting to IBM WebSphere Application Server...
      FATAL: null
      java.lang.StackOverflowError
      at java.lang.ClassLoader.loadClass(ClassLoader.java:668)
      ...

      Running the Jenkins service under:

      Oracle JDK 1.8, IBM JDK 1.8, and Oracle JDK 1.6

      results in it getting slightly farther, acknowledging the EAR file to deploy and not resulting in a StackOverFlowError: 

      ...
      Connecting to IBM WebSphere Application Server...
      The following artifacts will be deployed in this order...
      -------------------------------------------
      ProjectEar_201804171129AM.ear
      -------------------------------------------
      Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException:
      at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.getAppName(WebSphereDeploymentService.java:193)
      at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.getAppName(WebSphereDeploymentService.java:169)
      at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.getAppName(WebSphereDeployerPlugin.java:318)
      at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.createArtifact(WebSphereDeployerPlugin.java:275)
      at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.perform(WebSphereDeployerPlugin.java:197)
      at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
      at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
      at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
      at hudson.model.Build$BuildExecution.post2(Build.java:183)
      at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
      at hudson.model.Run.execute(Run.java:1783)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:89)
      at hudson.model.Executor.run(Executor.java:240)
      Caused by: com.ibm.websphere.management.application.client.AppDeploymentException: [Root exception is java.lang.IncompatibleClassChangeError: Implementing class]
      ...

      These excerpts are from the Jenkins GUI log. I've attached the console output of these, they have a few more details.

       

      As a note I've changed the projects runtime JDK of both Jenkins to IBM JDK6 and 8, Oracle JDK 6, 7, and 8. It doesn't seem to make a difference.

       

      As I read in the troubleshooting guide Jenkins runs the plugin based off the services JDK, which is what it appears to be doing. However using Oracle and IBM JDK 6 doesn't work either.

       

      Any ideas where I can go from here? Thanks.

       

       

          [JENKINS-50769] Deploying EAR to WAS 7 Issue with JDK

          Greg Peters added a comment -

          1) Is WAS v7 using the standard IBM JRE that's installed with WAS?
          2) I believe JDK 1.6 and WAS v7 .jar files the correct versions you need to deploy to WAS v7. Where JDK 1.6 is running Jenkins and the admin.jar and orb.jar files are copied directly from the WAS v7 server into the plugin classpath as outline in the Plugin documentation site.

          Greg Peters added a comment - 1) Is WAS v7 using the standard IBM JRE that's installed with WAS? 2) I believe JDK 1.6 and WAS v7 .jar files the correct versions you need to deploy to WAS v7. Where JDK 1.6 is running Jenkins and the admin.jar and orb.jar files are copied directly from the WAS v7 server into the plugin classpath as outline in the Plugin documentation site.

          Greg Peters added a comment -

          StackOverflow is duplicate and is related to using IBM JRE. The other issues are related to deploying to WebSphere with a mismatched version of Oracle JRE. If this server if WAS v7, sometimes WebSphere uses Java 1.5. Incompatible class errors are caused by the aforementioned issue

          Greg Peters added a comment - StackOverflow is duplicate and is related to using IBM JRE. The other issues are related to deploying to WebSphere with a mismatched version of Oracle JRE. If this server if WAS v7, sometimes WebSphere uses Java 1.5. Incompatible class errors are caused by the aforementioned issue

            gpeters Greg Peters
            chame Andrew Closs
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: