Weblogic server startup known errors and resolving

Mostly when we re-start Admin Server or managed servers you will be getting the following errors. These are very famous noted from the server logs

weblogic.management.ManagementException: 
            Unable to obtain lock on "Domain Path/servers/domainname/tmp/something.lok."
            Server may already be running

Remedy action

Go to this folder, rename the .lok file to .kol

Re-start the server again, You SHOULD see the following error

Could not obtain an exclusive lock for directory: 
            "Domain Path/servers/domainname/data/ldap/ldapfiles" 
            Waiting for 10 seconds and then retrying in case existing WebLogic Server is still shutting down

Remedy action

Go to this folder

rename the EmbeddedLDAP.lok to EmbeddedLDAP.kol

Re-start the servers again and YOU SHOULD SEE that the weblogic servers start correctly.

Read more...