<Error> <configfwk> <BEA-390101> <activation of session WebLogic F
Ailed: COM. Bea. WLI. config. Deployment. server. serverlockexception: failed to obtain WLS edit lock; I
T 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 refreshing Ming WLS changes which have yet to be activate
D. 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 Cu
Rrently held by user weblogic. This indicates that you have either started a WLS change and forgot
Ten to activate it, or another user is already Ming WLS changes which have yet to be activated.
WLS edit lock can be released by logging into WLS console and either releasing the lock or activat
Ing the pending WLS changes.
At com. Bea. WLI. config. Deployment. server. serverdeploymentinitiator. _ servercommit (unknown s
Ource)
At com. Bea. WLI. config. Deployment. server. serverdeploymentinitiator. Access $200 (unknown sourc
E)
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
>
Solution:
1. http: // localhost: 7001/console/
2. preferences
3. CancelAutomatically acquire lock and activate changes;
4. Return to sbconsole active