This content has been marked as final. Show 2 replies
One of the reasons for the managed server to go to ADMIN state is due to the failed deployments.
The failed deployments can be the failed deployments of the application(.war,.ear files) or due to failure in the creation of JDBC Resources/JMS Resources.
Please check in the logs if the managed server reports of any failed deployments.
Your idea worked and the issue is fixed..
The deployment /em WEBAPP had the target as "AdminServer" and "ManagedSerevr". I removed both and it works like a champ!!!
Thank you very much, Abhinav.