If we check from the first Admin Server , Its fine ( Deployments are in the active state)
But if we check after bringing the second admin server ( first Admin Server is still up , managed servers 1 & 2 are up , we haven't brought down anything ) , Deployments states are new/ Installed from the console of second Admin Server.
You can only have one Admin Server running on a domain. See the text below "It is up to you to make sure that you don’t have more than one admin server running at a time"
"The admin server is a WebLogic Server instance that runs some special
administrative applications like the WebLogic Console. Through these applications, the admin
server maintains a repository of configuration information for the domain, acts as a centralized location
for application deployment, and provides a browser-based administrative console application
that the administrator uses to configure, manage, and monitor all aspects of the domain."
"The last thing we want to discuss is how to handle admin server availability because the admin server
is not currently clusterable. This means that if the admin server goes down, you cannot administer your
WebLogic Server domain until you bring it back up. In most cases, you may not be too concerned if the
admin server goes down because all you need to do is restart it. If you use the node manager to start
the admin server, the node manager can automatically restart a failed admin server just like it can any
other server. What happens if the machine where the admin server runs fails in such a way that you
cannot restart the admin server? The answer is simple if you prepare for this unlikely event.
Proper operation of the admin server relies on several configuration files and any application files it
controls. Typically, the best thing to do is to store the admin server’s directory tree on a shared disk. As
long as the configuration and application files are accessible, you can restart the admin server on another
machine. It is up to you to make sure that you don’t have more than one admin server running at a time.
If the new machine can assume the original admin server’s Listen Address (or if it was not set), you
can simply start the admin server on the new machine without any configuration changes. Otherwise,
you will need to change the admin server’s Listen Address. Since the managed servers ping the admin
server URL every 10 seconds until it comes back up, you need to devise a way for the admin server URL
to allow the managed server to find the restarted admin server on the new IP address. The easiest way
to achieve that is using a DNS name that maps to both IP addresses, or better yet that is dynamically
updated to point to the correct location of the admin server. If this is a graceful shutdown and migration,
use the WebLogic Console to change the Listen Address just before shutting down the admin server. If
not, you will need to edit the config.xml file by hand to replace the old Listen Address with the new
one. Typically, we recommend planning ahead so that everything you need is already in place to make
admin server failover as painless as possible."