Race condition between admin and managed server?

Question

When I start my managed server, my admin server gets the following complaint
in its log file:
Jun 20, 2001 4:39:37 PM PDT Critical Log Management Unable to
contact managed server - rat5, at 172.16.1.26:7027
. Domain
logfile will not contain messages from this server.
java.lang.IllegalArgumentException: Invalid user name or password
     at
weblogic.management.logging.DomainLogHandler.getMBeanHome(DomainLogHandler.j
ava:281)
     at
weblogic.management.logging.DomainLogHandler.subscribeToServer(DomainLogHand
ler.java:243)
     at
weblogic.management.logging.DomainLogHandler.registerToMe(DomainLogHandler.j
ava:183)
     at java.lang.reflect.Method.invoke(Native Method)
     at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:562)
     at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
48)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at
weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(RemoteMBean
ServerImpl_WLSkel.java:382)
     at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
     at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
     at
weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.
java:118)
     at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
7)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
This happens while my managed server is still booting. It isn't listening on
port 7027 until a few seconds later. In the managed server rat5's log file
is
Jun 20, 2001 4:39:58 PM PDT Notice WebLogicServer WebLogic
Server started
Jun 20, 2001 4:39:58 PM PDT Notice WebLogicServer ListenThread
listening on port 7027
which is 21 seconds after the message in the admin log file. What do I have
to do to have the admin server wait until the managed server is up before
contacting it? Am I assessing the problem correctly?

Answer 1

nope
a server can be either Admin or Managed, there is no such thing as a Admin+Managed server.
A domain expects you to specify which instance is an Admin, in config.xml you find
<admin-server-name>AdminServer</admin-server-name>
But this is not a problem for you, to all effects a domain without any managed servers and with only 1 Admin is a perfectly legal environment,
you can deploy your applications to the Admin and be happy.
Actually this is a common setup for Development environments.
Of course in production you want to set up a proper environment with cluster etc....