Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

BEA-141297 - Could not get the server file lock

Following error is encountered when trying to start Oracle Weblogic Server:

<Info> <Management> <BEA-141297> <Could not get the server file lock. Ensure that another server is not running in the same directory. Retrying for another 60 seconds.>

How do I overcome this error and start the server?

like image 355
Catalin Ciolocoiu Avatar asked Nov 24 '15 08:11

Catalin Ciolocoiu


People also ask

Could not get the server file lock ensure that another server is not running?

The error means that there is a file lock that could not be released, as the server was previously not shut down correctly. In this case you must follow the next steps: Navigate to tmp folder in your $DOMAIN_HOME directory.

When a Weblogic server is stopped what are the lock files get deleted automatically?

Whenever you start any server, it creates lock files under $DOMAIN_HOME/servers/<server_name>/tmp with . lok extension and when you stop the server, it deletes these files automatically.

What is config lok in Weblogic?

config.lok The config. lok file is just used for getting a file lock on the config. xml file, in order to ensure that config file updates run serially. It will not cause any problems if it exists in the directory.

What is BEA home directory?

The BEA Home directory is a repository for common files that are used by multiple BEA products installed on the same machine. For this reason, the BEA Home directory can be considered a "central support directory" for the BEA products installed on your system.


1 Answers

The error means that there is a file lock that could not be released, as the server was previously not shut down correctly.

In this case you must follow the next steps:

  • Navigate to tmp folder in your $DOMAIN_HOME directory. (for example: C:\Oracle\Middleware\Oracle_Home\user_projects\domains\mydomain\servers\AdminServer\tmp)
  • Delete the lock file for the server instance, AdminServer.lok
  • Check if there are any java.exe processes are running, which should not be there. If there are any, they would have to be killed.
  • Restart your server
like image 93
2 revs Avatar answered Sep 23 '22 18:09

2 revs