此内容已被标记为最终。 显示 3 条回复
First, let me explain some basics about WebLogic:
1. WebLogic uses edit lock to make sure only one user can deploy application and change configuration at one time.
2. WebLogic automatically deploys applications under domain autodeploy/ directory when running in development.
In your case, someone is holding the edit lock before server starts, and you have an application called cartapp.ear under domain autodeploy directory. So the WebLogic autodeploy manager fails to deploy this application since it can not get the edit lock. An exception is thrown and the error message clearly indicates what the problem is. It works exactly as designed. That is why I <b>love</b> Weblogic.:-)
To fix the problem, just cancel the edit lock using Console or WLST. Restart the server, everything should be fine.
Edited by jzheng at 01/18/2008 8:34 AM
It would be nice if everything behaved as you describe. I clearly understand lock and edit mechanism that is introduced into WL version 10. NONE, I want to highlight, NONE is using the server except me - this is my developer machine. Same occures on other developer machine.
I would be more that glad if it worked as designed, but it doesn't seem to.
Just login the console and take control and edit, release it again, it will fix the issue, it works for me when I see this error.