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

View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Won't Fix
    • Labels:
      None
    • Environment:
      Jenkins 1.537, tomcat7, Ubuntu 12.04.3 LTS
    • Similar Issues:

      Description

      We faced to a problem with our Jenkins 1.537 into tomcat7; the tomcat7-tmp is full of war file.

      The problem have been put under the light when we started using wall display plug-in.
      We found out that it wasn't walldisplay that was causing this; but calls to the REST json api every 20 seconds.
      Calls are make on <JENKINS_URL>/job/<JOB_NAME>/api/json
      as you can see line 390 of this file : https://github.com/jenkinsci/walldisplay-plugin/blob/master/src/main/webapp/walldisplay.js

      The job also publish jar file but only war file is fulling the tomcat temp.

      We also see that not only REST api produce this temp war file! View the project page do this too.

      What we do not understand is why it's not happening to all job that publish war artifact...

      the job using:

      • remove old build
      • security based on project
      • launch on a windows slave
      • using Subversion
      • publish Checkstyle analysis
      • publish PMD analysis
      • save artifacts (jar and war using *)

      If it's not a bug from Jenkins it may be a tomcat7 configuration error?

        Attachments

          Activity

          Hide
          adoudev adoudev viaccess-orca added a comment - - edited

          We just tried to :

          • copy the job
          • remove artifact publish
          • launch the job
          • view job page
            => not more war file in tomcat temp
          • enable archiving artifact but NOT the war file
          • launch the job
          • view job page
            => war file in tomcat temp!
          Show
          adoudev adoudev viaccess-orca added a comment - - edited We just tried to : copy the job remove artifact publish launch the job view job page => not more war file in tomcat temp enable archiving artifact but NOT the war file launch the job view job page => war file in tomcat temp!
          Hide
          danielbeck Daniel Beck added a comment -

          Are you able to reproduce this issue on a vanilla installation of Jenkins 1.567? If so, please provide the exact + complete steps to reproduce the problem.

          Show
          danielbeck Daniel Beck added a comment - Are you able to reproduce this issue on a vanilla installation of Jenkins 1.567? If so, please provide the exact + complete steps to reproduce the problem.
          Hide
          adoudev adoudev viaccess-orca added a comment -

          I'm not able to reproduce it on a vanilla installation...

          I understand that it will be hard to debug if I can't reproduce it...

          Show
          adoudev adoudev viaccess-orca added a comment - I'm not able to reproduce it on a vanilla installation... I understand that it will be hard to debug if I can't reproduce it...
          Hide
          danielbeck Daniel Beck added a comment -
          • Are you running the vanilla instance also in Tomcat? If not, please try that.
          • Copy over all the files (not folders, they're just a cache) from the original Jenkins' "plugins" directory to get the same code running on your new instance.

          Either of these may be sufficient to reproduce the problem.

          If the latter works, you could try isolating the responsible plugin by selectively removing/adding plugins until the issue disappears.

          Show
          danielbeck Daniel Beck added a comment - Are you running the vanilla instance also in Tomcat? If not, please try that. Copy over all the files (not folders, they're just a cache) from the original Jenkins' "plugins" directory to get the same code running on your new instance. Either of these may be sufficient to reproduce the problem. If the latter works, you could try isolating the responsible plugin by selectively removing/adding plugins until the issue disappears.
          Hide
          adoudev adoudev viaccess-orca added a comment -

          I reproduced it

          Yes I was using a instance in tomcat7.

          I copied plugins jpi files in this vanilla installation.

          I will try to isolate the responsible plugin. FYI We have 87 jpi files...

          Show
          adoudev adoudev viaccess-orca added a comment - I reproduced it Yes I was using a instance in tomcat7. I copied plugins jpi files in this vanilla installation. I will try to isolate the responsible plugin. FYI We have 87 jpi files...
          Hide
          adoudev adoudev viaccess-orca added a comment -

          I found out!

          It is https://wiki.jenkins-ci.org/display/JENKINS/Cloudbees+Deployer+Plugin

          We have those line in the config.xml of the job; this config was not used and I thing wrong:

              <com.cloudbees.plugins.deployer.DeployNowJobProperty plugin="cloudbees-deployer-plugin@4.14.1">
                <oneClickDeploy>false</oneClickDeploy>
                <hosts>
                  <com.cloudbees.plugins.deployer.impl.run.RunHostImpl>
                    <targets class="java.util.Collections$UnmodifiableRandomAccessList" resolves-to="java.util.Collections$UnmodifiableList">
                      <c class="list">
                        <com.cloudbees.plugins.deployer.impl.run.RunTargetImpl>
                          <artifact class="com.cloudbees.plugins.deployer.sources.MavenArtifactDeploySource">
                            <groupId>xxxxxxxxxxxxx</groupId>
                            <artifactId>xxxxxxxxxxxx</artifactId>
                            <type>war</type>
                          </artifact>
                          <applicationConfig/>
                          <apiEndPoint>https://api.cloudbees.com/api</apiEndPoint>
                          <deploymentDescription>${JOB_NAME} #${BUILD_NUMBER}</deploymentDescription>
                          <deltaDeployment>false</deltaDeployment>
                          <clickStackConfig/>
                          <clickStackRuntimeConfig/>
                        </com.cloudbees.plugins.deployer.impl.run.RunTargetImpl>
                      </c>
                      <list reference="../c"/>
                    </targets>
                    <user></user>
                    <account></account>
                  </com.cloudbees.plugins.deployer.impl.run.RunHostImpl>
                </hosts>
              </com.cloudbees.plugins.deployer.DeployNowJobProperty>
          

          We removed this config and no more war file in the temp.

          Show
          adoudev adoudev viaccess-orca added a comment - I found out! It is https://wiki.jenkins-ci.org/display/JENKINS/Cloudbees+Deployer+Plugin We have those line in the config.xml of the job; this config was not used and I thing wrong: <com.cloudbees.plugins.deployer.DeployNowJobProperty plugin= "cloudbees-deployer-plugin@4.14.1" > <oneClickDeploy> false </oneClickDeploy> <hosts> <com.cloudbees.plugins.deployer.impl.run.RunHostImpl> <targets class= "java.util.Collections$UnmodifiableRandomAccessList" resolves-to= "java.util.Collections$UnmodifiableList" > <c class= "list" > <com.cloudbees.plugins.deployer.impl.run.RunTargetImpl> <artifact class= "com.cloudbees.plugins.deployer.sources.MavenArtifactDeploySource" > <groupId> xxxxxxxxxxxxx </groupId> <artifactId> xxxxxxxxxxxx </artifactId> <type> war </type> </artifact> <applicationConfig/> <apiEndPoint> https://api.cloudbees.com/api </apiEndPoint> <deploymentDescription> ${JOB_NAME} #${BUILD_NUMBER} </deploymentDescription> <deltaDeployment> false </deltaDeployment> <clickStackConfig/> <clickStackRuntimeConfig/> </com.cloudbees.plugins.deployer.impl.run.RunTargetImpl> </c> <list reference= "../c" /> </targets> <user> </user> <account> </account> </com.cloudbees.plugins.deployer.impl.run.RunHostImpl> </hosts> </com.cloudbees.plugins.deployer.DeployNowJobProperty> We removed this config and no more war file in the temp.
          Hide
          olamy Olivier Lamy added a comment -

          not used anymore

          Show
          olamy Olivier Lamy added a comment - not used anymore

            People

            • Assignee:
              pelle Christian Pelster
              Reporter:
              adoudev adoudev viaccess-orca
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: