While the log file of the OSB Server is like this:
<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. see log file for complete stacktrace sssd
sadasd
The reason for this error, is the fact the OSB is configured for automatic apply of changes made OSB. This option is default in OSB 10gR3 and should be switched off. This can be done via the WLS console.
- Logon to Console
- Select Preferences
- Uncheck the option "Automatically Acquire Lock and Activate Changes":
Click on Save - Activate Changes
