今天疯狂测试,一直在重启,重启。 结果出问题了;(
通过weblogic 9发布部署包之后启动weblogic,控制台报告以下错误,这个错误之前碰到过几次,但是有的时候通过在命令行停止服务,然后再重启可以解决,有的时候不能解决,于是乎,今天看了下这个问题,碰到这个问题的人很多,解决方式我只是找到了一种,错误日志类似如下:
<2009-12-8 上午10时01分22秒 CST> <Error> <Application Poller> <BEA-149408> <An exception occurred while deploying an application LendingSystemAPP: weblogic.management.ManagementException: weblogic.management.ManagementException: [Deployer:149164]The domain edit lock is owned by another session in exclusive mode - hence this deployment operation cannot proceed..
weblogic.management.ManagementException: weblogic.management.ManagementException: [Deployer:149164]The domain edit lock is owned by another session in exclusive mode - hence this deployment operation cannot proceed.
at weblogic.management.deploy.ApplicationsDirPoller.doActivate(ApplicationsDirPoller.java:246)
at weblogic.management.deploy.GenericAppPoller.doit(GenericAppPoller.java:275)
at weblogic.management.deploy.ApplicationsDirPoller.<init>(ApplicationsDirPoller.java:98)
at weblogic.management.deploy.ApplicationsDirPoller.<init>(ApplicationsDirPoller.java:108)
at weblogic.management.deploy.internal.DeploymentServerService.startAutoDeploymentPoller(DeploymentServerService.java:299)
Truncated. see log file for complete stacktrace
>
解决方式,不用关闭weblogic,直接进入控制台,登陆进入之后,看左上方的控制编辑状态,应该是处于锁定状态,也就是说“锁定并编辑”是灰色状态,点击下“释放配置”即可,要是不行的话,不要修改右边窗口的任何配置,点击保存,然后再点击“释放配置”,关闭weblogic,然后重启,问题就可以解决。
PS:
BEA-149164 Warning: The domain edit lock is owned by another session in exclusive mode - hence this deployment operation cannot proceed.
Description The domain edit lock is owned by another session in exclusive mode - hence this deployment operation cannot proceed.
Cause The domain edit lock is owned by another session in exclusive mode - hence this deployment operation cannot proceed.
Action Ensure the domain edit lock is available, and try again. If the problem persists, contact BEA support and provide the stack trace for further analysis.
这段英文没有很深的词,希望您能看明白。
In this case, be sure you click either Activate Changes or Release Configuration in the Change Center of the Administration Console and then rerun the deploy task