Issue:
If you get the below errors when starting the admin server or a managed server, follow the below steps in resolution
<Jul 31, 2012 10:16:15 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
<Jul 31, 2012 10:16:25 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
<Jul 31, 2012 10:16:35 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
<Jul 31, 2012 10:16:45 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
<Jul 31, 2012 10:16:55 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
Resolution:
Kill the hanging server start process (Kill -9 on the process ID)
Delete the edit.lok under the $DOMAIN_HOME and AdminServer.lok under the $DOMAIN_HOME/servers/<Server_Name>/tmp directory.
Restart the server
If you get the below errors when starting the admin server or a managed server, follow the below steps in resolution
<Jul 31, 2012 10:16:15 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
<Jul 31, 2012 10:16:25 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
<Jul 31, 2012 10:16:35 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
<Jul 31, 2012 10:16:45 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
<Jul 31, 2012 10:16:55 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
Resolution:
Kill the hanging server start process (Kill -9 on the process ID)
Delete the edit.lok under the $DOMAIN_HOME and AdminServer.lok under the $DOMAIN_HOME/servers/<Server_Name>/tmp directory.
Restart the server
No comments:
Post a Comment