When starting up the Oracle WebLogic 11g AdminServer, you may get the following error:
<Dec 3, 2010 8:57:32 AM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:Solution:
There are 1 nested errors:
weblogic.management.ManagementException: Unable to obtain lock on /u01/app/oracle/middleware/user_projects/domains/soa_domain/servers/AdminServer/tmp/AdminServer.lok. Server may already be running
at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:159)
at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:58)
at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:74)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:802)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:489)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
at weblogic.Server.main(Server.java:67)
>
<Dec 3, 2010 8:57:32 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Dec 3, 2010 8:57:32 AM EST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Dec 3, 2010 8:57:32 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
1. Shutdown the AdminServer gracefully as follows:
export MW_HOME=/u01/app/oracle/middleware
export DOMAIN_HOME=$MW_HOME/user_projects/domains/soa_domain
$DOMAIN_HOME/bin/stopWebLogic.sh2. Remove the lock file:
rm /u01/app/oracle/middleware/user_projects/domains/soa_domain/servers/AdminServer/tmp/AdminServer.lok3. Restart the AdminServer as follows, and you should be okay:
export MW_HOME=/u01/app/oracle/middlware
export DOMAIN_HOME=$MW_HOME/user_projects/domains/soa_domain
cd $DOMAIN_HOME/bin
nohup $DOMAIN_HOME/bin/startWebLogic.sh &Applicable Versions:
- Oracle WebLogic 11g (11.1.1.x)
No comments:
Post a Comment