"From translation MoS article" Weblogic adminserver start fail, error "unable to get file lock, would retry"

Weblogic adminserver start fail, error "Unable to get file lock, would retry"

Reference Original:
Weblogic AdminServer fails with "Unable to get file lock, would retry" error message (DOC ID 1613945.1)

Suitable for:
Oracle WebLogic server-version 8.1 and later
Information in this document applies to any platform.

Goal:
WebLogic Server startup times error:
<jan 7, 9:09:20 AM pst> <Info> <Management> <BEA-141281> <unable to get file lock, would re Try ...>
<jan 7, 9:09:30 AM pst> <Info> <Management> <BEA-141281> <unable to get file lock, would re Try ...>
<jan 7, 9:09:40 AM pst> <Info> <Management> <BEA-141281> <unable to get file lock, would re Try ...>
<jan 7, 9:09:50 AM pst> <Info> <Management> <BEA-141281> <unable to get file lock, would re Try ...>
<jan 7, 9:10:00 AM pst> <Info> <Management> <BEA-141281> <unable to get file lock, would re Try ...>

Solution:
When the server start time, a. Lok creates the file.

This document $fmw_home/servers/servername/tmp/servername.lok the next.

If the file exists, then it cannot be recreated, and the server cannot start.
The solution is to eliminate the existing Lok file or kill the process that is being held out of the file being executed.

"From translation MoS article" Weblogic adminserver start fail, error &quot;unable to get file lock, would retry&quot;