Deploying to Oracle Service bus not working

You created a simple business service in oracle workshop for weblogic and when you are trying to run the business service you are getting error


<Error> <ConfigFwk> <BEA-390101> <Activation of session OSB_Publish failed: com.bea.wli.config.deployment.server.ServerLockException: Failed to obtain WLS Edit lock; it is currently held by user weblogic. This indicates that you have either started a WLS change and forgotten to activate it, or another user is performing WLS changes which have yet to be activated. The WLS Edit lock can be released by logging into WLS console and either releasing the lock or activating the pending WLS changes. com.bea.wli.config.deployment.server.ServerLockException: Failed to obtain WLS Edit lock; it is currently held by user weblogic. This indicates that you have either started a WLS change and forgotten to activate it, or another user is performing WLS changes which have yet to be activated. The WLS Edit lock can be released by logging into WLS console and either releasing the lock or activating the pending WLS changes. at com.bea.wli.config.deployment.server.ServerDeploymentInitiator.__serverCommit(Unknown Source) at com.bea.wli.config.deployment.server.ServerDeploymentInitiator.access$200(Unknown Source) at com.bea.wli.config.deployment.server.ServerDeploymentInitiator$1.run(Unknown Source) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(Unknown Source) Truncated.

And your screen may look like this.




If you will go to details you will find the following details


The domain edit lock is owned by another session - this deployment operation requires exclusive access to the edit lock and hence
cannot proceed.
You can release the lock in Administration Console by first disabling "Automatically Acquire Lock and Activate Changes"
in Preference,
then clicking the Release Configuration button.


By default Automatically Acquire Lock and Activate Changes is activated in a weblogic console.

So in order to resolve the issue.


Log in to weblogic admin console

http://host:port/console


click on preference





NOw unselect the automatically acquire lock and activate changes and save the changes




NOw release the configuration and now you will be able to deploy the process from workshop