1. Developing SOA Applications with Oracle SOA Suite
  2. Completing Your Application
  3. Deploying SOA Composite Applications
  4. Testing and Troubleshooting
  5. Troubleshooting Common Deployment Errors
  6. Releasing Locks to Resolve ADF Task Form EAR File Deployment Errors

Releasing Locks to Resolve ADF Task Form EAR File Deployment Errors

If you deploy a SOA composite application JAR file and ADF task form EAR file, and the SOA JAR file is deployed successfully, but while deploying the EAR file, the following errors are displayed:

[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.

This error means you must first release the lock from Oracle WebLogic Server Administration Console to successfully deploy the EAR file.

To release locks to resolve ADF task form EAR file deployment errors:

  1. Log in to the Oracle WebLogic Server Administration Console.
  2. Below the console banner at the top of the page, click Preferences > User Preferences.
  3. Deselect Automatically Acquire Lock and Activate Changes.
  4. Click Save and note that buttons such as Lock and Edit and Release Configuration are visible.

    Note the following description that is displayed in the Oracle WebLogic Server Administration Console: 

    Automatically acquire the lock that enables configuration editing and
automatically activate changes as the user modifies, adds and deletes items
 (for example, when the user clicks the 'Save' button). This feature is not
 available in production mode.

This error can occur regardless of the deployment method you are using (for example, deploying through Oracle JDeveloper or through ant scripts).