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

Weblogic deployer plugin no such file or directory in base directory

    Details

    • Similar Issues:

      Description

      I'm giving resource path in job configuration but i'm getting below errors. 

       

      [EnvInject] - Loading node environment variables.
      Building in workspace /data/jenkins/workspace/Staging_MFHotfix_Deploy
      [Staging_MFHotfix_Deploy] $ /bin/sh -xe /tmp/jenkins1960089800202626129.sh
      + /data/jenkins/Weblogic/Script/getWarFile.sh 20170725 2144 mallfront.war
      scp: /mallfront.war: No such file or directory
      20170725 tarihli 2144 nolu mallfront.war Hotfix Paketi Ftpden kopyalandı
      [WeblogicDeploymentPlugin] - Pay attention to JDK version {selected version is 1.8.0_131} compatibility with WebLogic Deployer API (see Oracle documentation).
      [WeblogicDeploymentPlugin] - The JDK /usr/java/jdk1.8.0_131/jre will be used.
      [WeblogicDeploymentPlugin] - Retrieving artifacts recorded [filtered resources on mallfront.war]...
      [WeblogicDeploymentPlugin] - 2 files found under Script
      [WeblogicDeploymentPlugin] - the following resource recorded /data/jenkins/Weblogic/Script/mallfront.war is eligible.
      [WeblogicDeploymentPlugin] - the following resource ['getWarFile.sh'] doesn't match mallfront.war
      [WeblogicDeploymentPlugin] - Deploying the artifact on the following target : (name=MF_MO_AdminServer) (host=172.18.184.111) (port=17001)
      [WeblogicDeploymentPlugin] - UNDEPLOYING ARTIFACT...
      $ /usr/java/jdk1.8.0_131/jre/bin/java -Xms9216M -Xmx9216M -cp /data/jenkins/Weblogic/wlfullclient.jar weblogic.Deployer -debug -remote -verbose -noexit -name mallfront -targets MallFront1_1 -adminurl t3://172.18.184.111:17001 -user weblogic -password Qazxsw123 -undeploy
      [WeblogicDeploymentPlugin] - ARTIFACT UNDEPLOYED SUCCESSFULLY.
      [WeblogicDeploymentPlugin] - DEPLOYING ARTIFACT...
      $ /usr/java/jdk1.8.0_131/jre/bin/java -Xms9216M -Xmx9216M -cp /data/jenkins/Weblogic/wlfullclient.jar weblogic.Deployer -debug -stage -remote -verbose -upload -name mallfront -source '/data/jenkins/Weblogic/Script/mallfront.war' -targets MallFront1_1 -adminurl t3://172.18.184.111:17001 -user ****** -password ****** -deploy
      java.lang.RuntimeException: task completed abnormally (exit code = 1)
      at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.deploy(DeploymentTaskServiceImpl.java:239)
      at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.perform(DeploymentTaskServiceImpl.java:169)
      at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin.perform(WeblogicDeploymentPlugin.java:305)
      at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
      at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735)
      at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:676)
      at hudson.model.Build$BuildExecution.post2(Build.java:186)
      at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:621)
      at hudson.model.Run.execute(Run.java:1760)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:97)
      at hudson.model.Executor.run(Executor.java:405)
      ERROR: [WeblogicDeploymentPlugin] - Failed to deploy.
      [INFO] ------------------------------------------------------------------------
      [INFO] DEPLOYMENT FAILURE
      [INFO] ------------------------------------------------------------------------
      Build step 'Deploy the artifact to any WebLogic environments' changed build result to FAILURE

       

       

       

       

       

       

       

       

       

       

       

       

       

      ARTIFACT UNDEPLOYMENT ------------------------------------------------
      weblogic.Deployer invoked with options: -debug -remote -verbose -noexit -name mallfront -targets MallFront1_1 -adminurl t3://172.18.184.111:17001 -user weblogic -undeploy
      [WebLogicDeploymentManagerImpl.():119] : Constructing DeploymentManager for J2EE version V1_4 deployments
      [WebLogicDeploymentManagerImpl.getNewConnection():162] : Connecting to admin server at 172.18.184.111:17001, as user weblogic
      [ServerConnectionImpl.getEnvironment():295] : setting environment
      [ServerConnectionImpl.getEnvironment():298] : getting context using t3://172.18.184.111:17001
      [ServerConnectionImpl.getMBeanServer():246] : Connecting to MBeanServer at service:jmx:t3://172.18.184.111:17001/jndi/weblogic.management.mbeanservers.domainruntime
      [ServerConnectionImpl.getMBeanServer():246] : Connecting to MBeanServer at service:jmx:t3://172.18.184.111:17001/jndi/weblogic.management.mbeanservers.runtime
      [DomainManager.resetDomain():36] : Getting new domain
      [DomainManager.resetDomain():39] : Using pending domain: false
      [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@5e0826e7
      [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@5e0826e7
      [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7f0eb4b4
      [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7f0eb4b4
      [ServerConnectionImpl.initialize():178] : Connected to WLS domain: N11
      [ServerConnectionImpl.init():168] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl@130d63be
      [BasicOperation.dumpTmids():740] : Incoming tmids:
      [BasicOperation.dumpTmids():742] : {Target=MallFront1_1, WebLogicTargetType=server, Name=mallfront}, targeted=true
      [BasicOperation.deriveAppName():143] : appname established as: mallfront

      [BasicOperation.dumpTmids():740] : Incoming tmids:
      [BasicOperation.dumpTmids():742] : {Target=MallFront1_1, WebLogicTargetType=server, Name=mallfront}, targeted=true
      [BasicOperation.loadGeneralOptions():655] : Delete Files:false
      Timeout :3600000
      Targets:
      MallFront1_1
      ModuleTargets={}
      SubModuleTargets={}
      }
      Files:
      null
      Deployment Plan: null
      App root: null
      App config: null
      Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=null,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=mallfront,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=falsespecifiedTargetsOnly=false}

      [BasicOperation.execute():472] : Initiating undeploy operation for app, mallfront, on targets:
      [BasicOperation.execute():474] : MallFront1_1
      weblogic.management.ManagementException: [Deployer:149118]"mallfront" is not targeted to "MallFront1_1".
      at weblogic.utils.StackTraceDisabled.unknownMethod()
      [ServerConnectionImpl.close():341] : Closing DM connection
      [ServerConnectionImpl.close():361] : Unregistered all listeners
      [ServerConnectionImpl.closeJMX():381] : Closed JMX connection
      [ServerConnectionImpl.closeJMX():393] : Closed Runtime JMX connection
      [ServerConnectionImpl.closeJMX():405] : Closed Edit JMX connection
      Unexpected Error Initializing Deployer: weblogic.management.ManagementException: [Deployer:149118]"mallfront" is not targeted to "MallFront1_1".
      ------------------------------------ ARTIFACT DEPLOYMENT ------------------------------------------------
      weblogic.Deployer invoked with options: -debug -stage -remote -verbose -upload -name mallfront -source '/data/jenkins/Weblogic/Script/mallfront.war' -targets MallFront1_1 -adminurl t3://172.18.184.111:17001 -user weblogic -deploy
      [WebLogicDeploymentManagerImpl.():119] : Constructing DeploymentManager for J2EE version V1_4 deployments
      [WebLogicDeploymentManagerImpl.getNewConnection():162] : Connecting to admin server at 172.18.184.111:17001, as user weblogic
      [ServerConnectionImpl.getEnvironment():295] : setting environment
      [ServerConnectionImpl.getEnvironment():298] : getting context using t3://172.18.184.111:17001
      [ServerConnectionImpl.getMBeanServer():246] : Connecting to MBeanServer at service:jmx:t3://172.18.184.111:17001/jndi/weblogic.management.mbeanservers.domainruntime
      [ServerConnectionImpl.getMBeanServer():246] : Connecting to MBeanServer at service:jmx:t3://172.18.184.111:17001/jndi/weblogic.management.mbeanservers.runtime
      [DomainManager.resetDomain():36] : Getting new domain
      [DomainManager.resetDomain():39] : Using pending domain: false
      [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@5e0826e7
      [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@5e0826e7
      [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7f0eb4b4
      [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7f0eb4b4
      [ServerConnectionImpl.initialize():178] : Connected to WLS domain: N11
      [ServerConnectionImpl.setRemote():489] : Running in remote mode
      [ServerConnectionImpl.init():168] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl@130d63be
      [BasicOperation.dumpTmids():740] : Incoming tmids:
      [BasicOperation.dumpTmids():742] : {Target=MallFront1_1, WebLogicTargetType=server, Name=mallfront}, targeted=true
      [BasicOperation.deriveAppName():143] : appname established as: mallfront

      [BasicOperation.dumpTmids():740] : Incoming tmids:
      [BasicOperation.dumpTmids():742] : {Target=MallFront1_1, WebLogicTargetType=server, Name=mallfront}, targeted=true
      [BasicOperation.loadGeneralOptions():655] : Delete Files:false
      Timeout :3600000
      Targets:
      MallFront1_1
      ModuleTargets={}
      SubModuleTargets={}
      }
      Files:
      null
      Deployment Plan: null
      App root: /tmp/jenkins/./config/deployments/mallfront
      App config: /tmp/jenkins/./config/deployments/mallfront/plan
      Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=stage,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=mallfront,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=falsespecifiedTargetsOnly=false}

      java.io.FileNotFoundException: /'/data/jenkins/Weblogic/Script/mallfront.war' (No such file or directory)
      at java.io.FileInputStream.open0(Native Method)
      at java.io.FileInputStream.open(FileInputStream.java:195)
      at java.io.FileInputStream.(FileInputStream.java:138)
      at weblogic.utils.FileUtils.copy(FileUtils.java:266)
      at weblogic.utils.FileUtils.copy(FileUtils.java:245)
      at weblogic.utils.FileUtils.copy(FileUtils.java:186)
      at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.upload(ServerConnectionImpl.java:849)
      at weblogic.deploy.api.spi.deploy.internal.BasicOperation.uploadFiles(BasicOperation.java:332)
      at weblogic.deploy.api.spi.deploy.internal.BasicOperation.execute(BasicOperation.java:465)
      at weblogic.deploy.api.spi.deploy.internal.BasicOperation.run(BasicOperation.java:178)
      at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.deploy(WebLogicDeploymentManagerImpl.java:390)
      at weblogic.deploy.api.tools.deployer.DeployOperation.execute(DeployOperation.java:51)
      at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:139)
      at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
      at weblogic.utils.compiler.Tool.run(Tool.java:158)
      at weblogic.utils.compiler.Tool.run(Tool.java:115)
      at weblogic.Deployer.run(Deployer.java:74)
      at weblogic.Deployer.main(Deployer.java:55)
      [ServerConnectionImpl.close():341] : Closing DM connection
      [ServerConnectionImpl.close():361] : Unregistered all listeners
      [ServerConnectionImpl.closeJMX():381] : Closed JMX connection
      [ServerConnectionImpl.closeJMX():393] : Closed Runtime JMX connection
      [ServerConnectionImpl.closeJMX():405] : Closed Edit JMX connection

       

       

      Finished: FAILURE

        Attachments

          Activity

          Hide
          mariano92 Mariano added a comment -

          Raphael CHAUMIER ,

          I was testing and performing correctly.

          With respect to the JDK configuration, I used it in Maven projects that require Java 1.7 but the Deployment is done in WebLogic 10.3.6 (which requires JDK 1.6)

          Thank you very much!

          Show
          mariano92 Mariano added a comment - Raphael CHAUMIER , I was testing and performing correctly. With respect to the JDK configuration, I used it in Maven projects that require Java 1.7 but the Deployment is done in WebLogic 10.3.6 (which requires JDK 1.6) Thank you very much!
          Hide
          raphc Raphael CHAUMIER added a comment -

          Yes Mariano

          I removed this feature cause I don't see any reason to set the jdk in job configuration. The JDK version mainly depends of weblogic client libraries which are configured in global configuration where JDK is also defined.

          Did you use it ?

          As it works, I will close the issue.

          Regards

           

           

          Show
          raphc Raphael CHAUMIER added a comment - Yes Mariano I removed this feature cause I don't see any reason to set the jdk in job configuration. The JDK version mainly depends of weblogic client libraries which are configured in global configuration where JDK is also defined. Did you use it ? As it works, I will close the issue. Regards    
          Hide
          mariano92 Mariano added a comment - - edited

          Hi Raphael CHAUMIER,

          Upgrade to version 4.0 and work properly.

          Another question, is the JDK configuration within Job no longer available?

          Greetings and thank you very much
          Mariano

          Show
          mariano92 Mariano added a comment - - edited Hi Raphael CHAUMIER , Upgrade to version 4.0 and work properly. Another question, is the JDK configuration within Job no longer available? Greetings and thank you very much Mariano
          Hide
          raphc Raphael CHAUMIER added a comment -

          Hi suleyman idinak and Mariano

          I've just released the version 4.0. Let me know if it's ok for you.

          Show
          raphc Raphael CHAUMIER added a comment - Hi suleyman idinak and Mariano I've just released the version 4.0. Let me know if it's ok for you.
          Hide
          raphc Raphael CHAUMIER added a comment -

          Hi suleyman idinak and Mariano

           

          It's a regression on 3.7 version. You should downgrade to 3.6 up to the 4.0 will be released.

           

          Regards

          Show
          raphc Raphael CHAUMIER added a comment - Hi  suleyman idinak and Mariano   It's a regression on 3.7 version. You should downgrade to 3.6 up to the 4.0 will be released.   Regards
          Hide
          mariano92 Mariano added a comment -

          Hi suleyman,

          I have the same issue with this plugin for weblogic.
          Jenkins Version: 2.71 (LTS)
          Plugin Version: 3.7
          Operating System: Centos 7 64-bit

          i currently have another jenkins version (2.52 weekly) installed in Windows 7 64 bits, with the weblogic plugin 3.6 working correctly.

          I compared the configuration for both jenkins and they turned out the same.

          My question is, are you sure it's a bug in the plugin? or a particular configuration for centos may be needed?

          Thank you

          Show
          mariano92 Mariano added a comment - Hi suleyman, I have the same issue with this plugin for weblogic. Jenkins Version: 2.71 (LTS) Plugin Version: 3.7 Operating System: Centos 7 64-bit i currently have another jenkins version (2.52 weekly) installed in Windows 7 64 bits, with the weblogic plugin 3.6 working correctly. I compared the configuration for both jenkins and they turned out the same. My question is, are you sure it's a bug in the plugin? or a particular configuration for centos may be needed? Thank you

            People

            • Assignee:
              raphc Raphael CHAUMIER
              Reporter:
              suloman1903 suleyman idinak
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: