Weblogic Fails To Start With Error “Unable to obtain lock”

September 9, 2010 3 Comments

<23-Jul-2009 12:57:00 o’clock BST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

weblogic.management.ManagementException: Unable to obtain lock on /opt/bea/user_projects/domains/ORACLE_COMMUNICATIONS/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:75)
        at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:374)
        at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:125)

To start the server again:

  • find -name “*.DAT” files in user_projects/domains/base_domains directory (in our case!) and move or remove them
  • remove “EmbeddedLDAP.lok” and “AdminServer.lok” (maybe some more)
  • netstat -lntp to find out which process listen to your serverport, kill this via kill -TERM
  • Start the weblogic server using the command : nohup ./startWebLogic.sh > /tmp/startWebLogic.txt &

Filed under 11gR1

About mpoojari
Oracle Consultant and Solutions Architect

3 Responses to Weblogic Fails To Start With Error “Unable to obtain lock”

  1. Morrighu Badb (@Morrighu) says:
    May 24, 2012 at 10:39 pm

    I’m officially starting to HATE oracle. I don’t have any DAT files. I don’t have either the EmbeddedLDAP.lok or the AdminServer.lok. I tried to touch the AdminServer.lok to see if it was because the file didn’t exist. Same error message. I’ve killed every single process but SSH. And it still doesn’t start because of this AdminServer.lok error message.

    Reply
    • mpoojari says:
      May 27, 2012 at 9:26 am

      Hi

      This problem sometimes occurs if you killed the bin/startWebLogic process via kill command.

      Could you paste here the log file messages.

      Thanks

      Mohan

      Reply
  2. somu desai says:
    October 20, 2016 at 8:06 am

    Go to taskmanager->Process and search java.exe and kill that process

    Reply

Leave a comment