4 Replies Latest reply on Oct 7, 2009 3:11 AM by CharanB

    weblogic deploy ant script error

    704689
      Hi,

      I was deploying a war file using wldeploy
      could you guys check the following error and tell me what can be done to resolve?

      $ ant deploy-war
      Buildfile: build.xml

      login:
      Password:
      [exec] Warning: no access to tty (Bad file descriptor).
      [exec] Thus no job control in this shell.

      deploy-war:
      Trying to override old definition of datatype wldeploy
      [wldeploy] weblogic.Deployer -debug -verbose -noexit -name calendar -source /export/home/cramired/Calendar.war -targets ibu-sharedMS0120007 -adminurl t3://10.249.15.31:10007 -user admin -password ******** -deploy
      [wldeploy] weblogic.Deployer invoked with options: -debug -verbose -noexit -name calendar -source /export/home/cramired/Calendar.war -targets ibu-sharedMS0120007 -adminurl t3://10.249.15.31:10007 -user admin -deploy
      [wldeploy] [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
      [wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at 10.249.15.31:10007, as user admin
      [wldeploy] [ServerConnectionImpl.getEnvironment():288] : setting environment
      [wldeploy] [ServerConnectionImpl.getEnvironment():291] : getting context using t3://10.249.15.31:10007
      [wldeploy] [ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:t3://10.249.15.31:10007/jndi/weblogic.management.mbeanservers .domainruntime
      [wldeploy] [ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:t3://10.249.15.31:10007/jndi/weblogic.management.mbeanservers .runtime
      [wldeploy] [DomainManager.resetDomain():36] : Getting new domain
      [wldeploy] [DomainManager.resetDomain():39] : Using pending domain: true
      [wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification list ener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@83d8be
      [wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@83d8be
      [wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@1db6942
      [wldeploy] [MBeanCache.addNotificationListener():103] : Added notification list ener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@1db6942
      [wldeploy] [ServerConnectionImpl.initialize():171] : Connected to WLS domain: ibu-shared
      [wldeploy] [ServerConnectionImpl.init():161] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl@11ed166
      [wldeploy] [BasicOperation.dumpTmids():689] : Incoming tmids:
      [wldeploy] [BasicOperation.dumpTmids():691] : {Target=ibu-sharedMS0120007, We                                                                             bLogicTargetType=server, Name=calendar}, targeted=true
      [wldeploy] [BasicOperation.deriveAppName():140] : appname established as: calendar
      [wldeploy] <Sep 1, 2009 12:21:09 AM PDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, calendar [archive: /export/home/cramired/Calendar.war], to ibu-sharedMS0120007 .>
      [wldeploy] [BasicOperation.dumpTmids():689] : Incoming tmids:
      [wldeploy] [BasicOperation.dumpTmids():691] : {Target=ibu-sharedMS0120007, We                                                                             bLogicTargetType=server, Name=calendar}, targeted=true
      [wldeploy] [BasicOperation.loadGeneralOptions():606] : Delete Files:false
      [wldeploy] Timeout :3600000
      [wldeploy] Targets:
      [wldeploy] ibu-sharedMS0120007
      [wldeploy] ModuleTargets={}
      [wldeploy] SubModuleTargets={}
      [wldeploy] }
      [wldeploy] Files:
      [wldeploy] null
      [wldeploy] Deployment Plan: null
      [wldeploy] App root: /tmp/cramired/./config/deployments/calendar
      [wldeploy] App config: /tmp/cramired/./config/deployments/calendar/plan
      [wldeploy] Deployment Options: {isRetireGracefully=true,isGracefulProductionToA                                                                             dmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1                                                                             ,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,                                                                             libSpecVersion=null,libImplVersion=null,stageMode=null,clusterTimeout=3600000,al                                                                             tDD=null,altWlsDD=null,name=calendar,securityModel=null,securityValidationEnable                                                                             d=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSu                                                                             bmoduleTargets=true,timeout=0deploymentPrincipalName=null}

      [wldeploy] [BasicOperation.execute():423] : Initiating deploy operation for app , calendar, on targets:
      [wldeploy] [BasicOperation.execute():425] : ibu-sharedMS0120007
      [wldeploy] weblogic.management.ManagementException: [Deployer:149163]The domain edit lock is owned by another session in non-exclusive mode - this deployment operation requires exclusive access to the edit lock and hence cannot proceed. If you are using "Automatically Aquire Lock and Activate Changes" in the console, then the lock will expire shortly so retry this operation.
      [wldeploy] at weblogic.deploy.internal.adminserver.operations.AbstractOpera tion.execute(AbstractOperation.java:203)
      [wldeploy] at weblogic.management.deploy.internal.DeployerRuntimeImpl$2.run (DeployerRuntimeImpl.java:817)
      [wldeploy] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Auth enticatedSubject.java:321)
      [wldeploy] at weblogic.security.service.SecurityManager.runAs(Unknown Sourc e)
      [wldeploy] at weblogic.management.deploy.internal.DeployerRuntimeImpl.perfo rmDeployerActions(DeployerRuntimeImpl.java:811)
      [wldeploy] at weblogic.management.deploy.internal.DeployerRuntimeImpl.deplo y(DeployerRuntimeImpl.java:411)
      [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces\sorImpl.java:39)
      [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet hodAccessorImpl.java:25)
      [wldeploy] at java.lang.reflect.Method.invoke(Method.java:597)
      [wldeploy] at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSMo delMBean.java:437)
      [wldeploy] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke( DefaultMBeanServerInterceptor.java:836)
      [wldeploy] at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
      [wldeploy] at weblogic.management.mbeanservers.domainruntime.internal.Feder atedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:255)
      [wldeploy] at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptor Base$16.run(WLSMBeanServerInterceptorBase.java:447)
      [wldeploy] at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptor Base.invoke(WLSMBeanServerInterceptorBase.java:445)
      [wldeploy] at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOp sInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:65)
      [wldeploy] at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptor Base$16.run(WLSMBeanServerInterceptorBase.java:447)
      [wldeploy] at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptor Base.invoke(WLSMBeanServerInterceptorBase.java:445)
      [wldeploy] at weblogic.management.mbeanservers.internal.SecurityInterceptor .invoke(SecurityInterceptor.java:443)
      [wldeploy] at weblogic.management.mbeanservers.internal.AuthenticatedSubjec tInterceptor$10$1.run(AuthenticatedSubjectInterceptor.java:582)
      [wldeploy] at weblogic.management.mbeanservers.internal.AuthenticatedSubjec tInterceptor$10.run(AuthenticatedSubjectInterceptor.java:580)
      [wldeploy] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Auth enticatedSubject.java:363)
      [wldeploy] at weblogic.management.mbeanservers.internal.AuthenticatedSubjec tInterceptor.invoke(AuthenticatedSubjectInterceptor.java:573)
      [wldeploy] at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLS MBeanServer.java:307)
      [wldeploy] at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMI ConnectionImpl.java:1426)
      [wldeploy] at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIC onnectionImpl.java:72)
      [wldeploy] at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOpera tion.run(RMIConnectionImpl.java:1264)
      [wldeploy] at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOpe ration(RMIConnectionImpl.java:1366)
      [wldeploy] at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
      [wldeploy] at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
      [wldeploy] at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
      [wldeploy] at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
      [wldeploy] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Auth enticatedSubject.java:363)
      [wldeploy] at weblogic.security.service.SecurityManager.runAs(Unknown Source)
      [wldeploy] at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
      [wldeploy] at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
      [wldeploy] at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
      [wldeploy] at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
      [wldeploy] [ServerConnectionImpl.close():334] : Closing DM connection
      [wldeploy] [ServerConnectionImpl.close():354] : Unregistered all listeners
      [wldeploy] [ServerConnectionImpl.closeJMX():374] : Closed JMX connection
      [wldeploy] [ServerConnectionImpl.closeJMX():386] : Closed Runtime JMX connection
      [wldeploy] [ServerConnectionImpl.closeJMX():398] : Closed Edit JMX connection

      BUILD FAILED
      /export/home/cramired/build.xml:71: weblogic.management.ManagementException: [De                                                                             ployer:149163]The domain edit lock is owned by another session in non-exclusive mode - this deployment operation requires exclusive access to the edit lock and hence cannot proceed. If you are using "Automatically Aquire Lock and Activate Changes" in the console, then the lock will expire shortly so retry this operation.


      Thanks,
      Charan
        • 1. Re: weblogic deploy ant script error
          716508
          /export/home/cramired/build.xml:71: weblogic.management.ManagementException: De ployer:149163The domain edit lock is owned by another session in non-exclusive mode - this deployment operation requires exclusive access to the edit lock and hence cannot proceed. If you are using "Automatically Aquire Lock and Activate Changes" in the console, then the lock will expire shortly so retry this operation.

          Are you using WLS 10.3 please open the console and goto preference in the top menu
          Preference  Advance Option  automatically aquire lock and Activate changes
          It is checked by default uncheck it and then release the lock and run the ant task.

          Regards
          Ravi Dahal
          • 2. Re: weblogic deploy ant script error
            704689
            Automatically Acquire Lock and Activate Changes is set to false

            is this related to file permissions in linux.

            I'm running the ant script with the username "escoe"

            but the weblogic 10 owner is "svc-wls10"

            production mode has been enabled in my WLS 10.3.

            is this related to Acquire Lock?

            Edited by: Charan Ramireddy on Sep 1, 2009 8:17 AM
            • 3. Re: weblogic deploy ant script error
              674225
              You can try using "-usenonexclusivelock" in wldeploy
              • 4. Re: weblogic deploy ant script error
                CharanB
                can this be used in wldeploy ant task