Problem:
When using the startWebLogic.sh to start up the AdminServer, you may receive the following error:
Solution:
1. Simply delete the offending lock file:
Applicable Versions:
When using the startWebLogic.sh to start up the AdminServer, you may receive the following error:
<Aug 13, 2012 10:53:09 AM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
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:880)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:570)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:467)
at weblogic.Server.main(Server.java:71)
>
1. Simply delete the offending lock file:
rm -f /u01/app/oracle/middleware/user_projects/domains/soa_domain/servers/AdminServer/tmp/AdminServer.lok2. Restart the AdminServer:
cd $DOMAIN_HOME
nohup ./startWebLogic.sh &
Applicable Versions:
- Oracle WebLogic Server 11g (11.1.1.5)
No comments:
Post a Comment