Issue:
weblogic.management.ManagementException: Booting as admin server, but servername, osb_mngd_srvr_1, does not match the admin server name, AdminServer
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
at weblogic.Server.main(Server.java:71)
>
Reason:
nmStart will look for boot.properties and startup.properties files when trying to start a managed server. If it does not find these files, it will assume that it is starting an Admin Server.
Also, even if these files are manually created, nmStart would start the managed server in MSI (Managed Server Independence) mode.
So, WebLogic recommends starting the managed servers using the "start" WLST command instead of "nmStart" command.
"Using the start command causes WLST to contact the Administration Server to determine the Managed Servers startup properties. These are in turn passed to Node Manager and are used to start the Managed Server."
Thus, the managed server will still be monitored by the node manager.
Also, even if these files are manually created, nmStart would start the managed server in MSI (Managed Server Independence) mode.
So, WebLogic recommends starting the managed servers using the "start" WLST command instead of "nmStart" command.
"Using the start command causes WLST to contact the Administration Server to determine the Managed Servers startup properties. These are in turn passed to Node Manager and are used to start the Managed Server."
Thus, the managed server will still be monitored by the node manager.
Resolution:
"The following general procedures are recommended for starting a Managed Server using WLST and Node Manager.
1. Start Node Manager. See Starting Node Manager.
2. Start an Administration Server. See Starting Instances of WebLogic Server in Managing Server Startup and Shutdown.
3. Invoke WLST and connect to an Administration Server using the connect command.
4. Start your Managed Server using the WLST start command."
So, please do not use nmStart to start your managed server especially when you are starting for the first time.
Start the managed server using the "start" WLST command as explained in the above steps .
1. Start Node Manager. See Starting Node Manager.
2. Start an Administration Server. See Starting Instances of WebLogic Server in Managing Server Startup and Shutdown.
3. Invoke WLST and connect to an Administration Server using the connect command.
4. Start your Managed Server using the WLST start command."
So, please do not use nmStart to start your managed server especially when you are starting for the first time.
Start the managed server using the "start" WLST command as explained in the above steps .
Hence while running Managed Server for the first time use below commands:
· Got 'C:/Oracle/Middleware_weblogic\wlserver_10.3\server\bin and run setWLSEnv.cmd
· Run Java weblogic.WLST
· connect('weblogic','welcome1','t3://10.50.64.42:7001') –Connect to Admin Server
· start('osb_mngd_srvr_1','Server','t3://10.50.64.42:7002')—Start Managed Server
