Weblogic Parallel Applications Deployment

Question

By parallel applications deployment, I'm talking about getting rid of the edit lock error in Weblogic deployment.

[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. -> [Help 1]

I've done my research through google, stackoverflow and oracle itself and got nothing.

I believed AS powerful like Weblogic should have covered this feature, could anyone help me out here?

**EDIT 1: ** I am doing deployment via some Ant scripts, so parallel deployment is really what i need.

**EDIT 2: ** I need to do parallel deployment via some automation like Ant or Maven, so unlock manually is really not my option...

Answer 1

Go to weblogic admin console say in localhost:7001 and in the left see if you have released the configuration , ie. 'Release Configuration' button is greyed or not. If not. click that and then try to redeploy from your IDE. That worked for me at least :) Good luck !

Answer 2

I have the same problem, with my nightly build deployments.

The documentation tells you to use nonexclusive deployment mode:

usenonexclusivelock

Specifies that the deployment action (deploy, redeploy, stop, and so on) uses the existing lock on the domain that has already been acquired by the same 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.

Source: http://docs.oracle.com/cd/E17904_01/web.1111/e13706/wldeploy.htm#i1022929

Ant example: http://adfhowto.blogspot.de/2011/07/troubleshooting-domain-edit-lock-is.html

weblogic.Deployer example:

java weblogic.Deployer -debug -remote -verbose -name MyWebApp -source MyWebApp.ear -targets server1 -adminurl t3://localhost:7001 -user weblogic -deploy -stage -upload -usenonexclusivelock

Answer 3

Click on Release Configuration button (if showing in enabled mode) to release the lock. This solved my issue.

Answer 4

It seems previous modification of the configuration was not committed. It can happen if you modified the configuration e.g. through console but forget to commit.

Open the admin console (default - http://localhost:7101/console) log in. After successful login look in the upper left corner. There you see a button where you can activate pending changes (or revoke them). Then retry the deployment.

Peter