Failed to obtain WLS Edit lock

最新推荐文章于 2024-07-12 11:31:29 发布

鸿风

最新推荐文章于 2024-07-12 11:31:29 发布

阅读量2k

点赞数

分类专栏： ESB 文章标签： logging weblogic user session file

本文链接：https://blog.csdn.net/feng1603/article/details/6669473

版权

ESB 专栏收录该内容

5 篇文章 0 订阅

订阅专栏

<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 performing 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 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 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

解决办法:

1、http://localhost:7001/console/

2、Preferences

3、取消 Automatically Acquire Lock and Activate Changes ；

4、返回 sbconsole active