If you start up a WebLogic managed server using the startManagedWebLogic.sh script, you may see the following exception in the logs:
<Apr 14, 2019 2:34:42,929 PM EDT> <Critical> <ConsensusLeasing> <BEA-000001> <Server must be started by Node Manager when consensus leasing is enabled.> <Apr 14, 2019 2:34:45,345 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: Server must be started by NodeManager when consensus leasing is enabled>
As a Critical error, the managed server would not start up as a result.
To resolve this:
- Login to the WebLogic Admin Console
- Navigate to Clusters > [cluster_name] > Configuration > Migration
- Change the Migration Basis from 'Consensus' to 'Database'
- Select a valid Data Source
Database leasing requires the availability of a high-availability database, such as Oracle RAC, to store leasing information.
Consensus leasing stores the leasing information in-memory within a cluster member. This option requires Node Manager to be configured and running, and you can only start the managed server using Node Manager.
Unless you are setting up and configuring migratable servers (I hope not!), it doesn't matter what you set this to.
In case I'm not clear, migratable servers and migratable services are generally a bad idea.