Script-Based Node Manager Fails to Start Managed Server with BEA-300047: AdminServerTag.lck: Not a Directory (Doc ID 1317221.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Weblogic Server - Version 10.3.3 and later
Information in this document applies to any platform.

Symptoms

When using Script Based Node Manager to start the servers from your domain, there's a possibility that during server startup, the Node Manager might create a file called AdminServertag under %Domain_Home%/servers/.  Further, if the WebLogic Server data source is configured using Consensus Leasing, the Node Manager is also in charge of getting the states of the servers.

When the Node Manager tries to read the servers folder and aquire a lock on this AdminServertag file, the managed server fails to start. The following error message is generated:

 

<> <> <c33a6003fa0a3382:-26ee4f55:12d86474db4:-7fe7-000000000004ac9c> <1295264024741> <BEA-300047> <getStates
weblogic.nodemanager.NMException: rm: cannot remove `/opt/soauser/domains/OSB_TSTR2_DOMAIN/servers/AdminServerTag/data/nodemanager/AdminServerTag.lck': Not a
directory
at weblogic.nodemanager.client.ShellClient.checkResponse(ShellClient.java:426)
at weblogic.nodemanager.client.ShellClient.access$200(ShellClient.java:28)
at weblogic.nodemanager.client.ShellClient$NMCommandRunner.run(ShellClient.java:548)
>

 

Changes


The issue is caused when configuring the WebLogic managed servers as migratable targets and with database Consensus Leasing. With this configuration, servers must be started using wlscontrol.sh.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms