Raphael CHAUMIER added a comment - 2015-11-07 22:07 - edited Hi, It seems that the connection is established but the client doesn't send any data. Do you have more log on jenkins logs ? Is the ear/jar/war you want to deploy correctly selected? Regards

simba s added a comment - 2015-11-09 04:10 Thank you so much for looking at.It is EAR file deploying into Weblogic server. Jenkins server is on Windows 7. Weblogic12c server is on Linux 8.4 . Below is the complete Log. weblogic.Deployer invoked with options: -debug -stage -remote -verbose -upload -name appName -source C:\appName\app.ear -targets appCluster -adminurl t3://url.com:8455 -user weblogic -deploy [WebLogicDeploymentManagerImpl.<init>():119] : Constructing DeploymentManager for J2EE version V1_4 deployments [WebLogicDeploymentManagerImpl.getNewConnection():162] : Connecting to admin server at url.com:8455, as user weblogic [ServerConnectionImpl.getEnvironment():295] : setting environment [ServerConnectionImpl.getEnvironment():298] : getting context using t3://url.com:8455 [ServerConnectionImpl.getMBeanServer():246] : Connecting to MBeanServer at service:jmx:t3://url.com:8455/jndi/weblogic.management.mbeanservers.domainruntime [ServerConnectionImpl.getMBeanServer():246] : Connecting to MBeanServer at service:jmx:t3://url.com:8455/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@3315d2d7 [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@3315d2d7 [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@31e5415e [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@31e5415e [ServerConnectionImpl.initialize():178] : Connected to WLS domain: app-domain [ServerConnectionImpl.setRemote():489] : Running in remote mode [ServerConnectionImpl.init():168] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl@2fd1433e [BasicOperation.dumpTmids():740] : Incoming tmids: [BasicOperation.dumpTmids():742] : {Target=appCluster, WebLogicTargetType=cluster, Name=appName}, targeted=true [BasicOperation.deriveAppName():143] : appname established as: appName <Oct 10, 2015 8:40:06 AM EDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, appName [archive: C:\app.ear] , to appCluster .> [BasicOperation.dumpTmids():740] : Incoming tmids: [BasicOperation.dumpTmids():742] : {Target=appCluster, WebLogicTargetType=cluster, Name=appName} , targeted=true [BasicOperation.loadGeneralOptions():655] : Delete Files:false Timeout :3600000 Targets: appCluster ModuleTargets={} SubModuleTargets={} } Files: null Deployment Plan: null App root: c:\user\.\config\deployments\appName App config: c:\user\.\config\deployments\appName\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=appName,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=falsespecifiedTargetsOnly=false} weblogic.deploy.api.internal.utils.DeployerHelperException: The source 'C:\Users\Local\Temp\app.ear414919056335932' for the application 'appName' could not be loaded to the server 'http://url.com:8455/bea_wls_deployment_internal/DeploymentService'. Software caused connection abort: socket write error at weblogic.deploy.api.internal.utils.JMXDeployerHelper.uploadSource(JMXDeployerHelper.java:677) at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.upload(ServerConnectionImpl.java:857) 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

Raphael CHAUMIER added a comment - 2015-11-09 14:36 I don't see anything curious. Do you use the advanced configuration to execute the deploy or not ? If you execute directly the following command. What's happens ? java -cp /path/to/weblogic.jar weblogic.Deployer -debug -stage -remote -verbose -upload -name appName -source C:\appName\app.ear -targets appCluster -adminurl t3://url.com:8455 -user weblogic -deploy

Raphael CHAUMIER added a comment - 2016-01-09 17:22 Hi, Can I close the issue ? Regards

simba s added a comment - 2016-01-10 17:11 yes Please. Thank you.