Home > Weblogic Portal, Weblogic Server, WSRP > wldeploy:Exclusive access to the edit lock

wldeploy:Exclusive access to the edit lock

This error is thrown when deploying an applicaton on Weblogic Server with wldeploy task.


<Nov 17, 2010 10:45:18 AM EST> <Warning> <Deployer> <BEA-149124> <Failures were detected while initiating deploy task for application 'MyWSRPProducer'. Error is: '[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.'> 

One of the following 2 solutions can be adapted to get rid of the error:

  1. Login to Admin console at http://localhost:7001/console and be sure you click either Activate Changes or Release Configuration in the Change Center and then rerun the deploy task

  2. Using usenonexclusivelock flag on the wldeploy task to use the existing lock on the domain that has already been acquired by the user performing the action.This attribute is particularly useful when the user is using multiple deployment tools (Ant task, command line, Administration console, and so on) simultaneously and one of the tools has already acquired a lock on the domain. Valid values for this attribute are true and false. Default value is false
  1. No comments yet.
  1. No trackbacks yet.

Leave a comment