Enterprise Manager Fusion Middleware Control (fmwc) 11g Shows Managed Server As DOWN Even When The Managed Server Is RUNNING
Last updated on MAY 01, 2017
Applies to:Enterprise Manager for Fusion Middleware - Version 18.104.22.168.0 to 22.214.171.124.0
Enterprise Manager for Fusion Middleware - Version 126.96.36.199.0 to 188.8.131.52.0
Information in this document applies to any platform.
Enterprise Manager Fusion Middleware Console (fmwc) 11g shows a managed server e.g.WLS_FORMS, WLS_Reports as DOWN (red arrow).
The managed server is running and can be used, however EM console reports them as DOWN.
The following lines are seen in the managed server log:
<Jun 17, 2011 9:18:34 AM CEST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://localhost:<adminserver_port>/.>
####<Jun 17, 2011 9:19:22 AM CEST> <Warning> <JMX> <abc.corp> <ServerName> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1308295162973> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at <JMXServiceURL:null>.>
It is not possible to connect to the AdminServer using localhost via WLST:
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3://localhost:<adminserver_port>
Use dumpStack() to view the full stacktrace
It is possible to connect using the hostname but the managed server cannot be seen in WLST:
Connecting to t3://<hostname>:<adminserver_port> with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'MyDomain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)
If the managed server has successfully connected with the AdminServer you should see:
As there is no <ServerName> this means it has been unable to contact the AdminServer at t3://localhost:<adminserver_port> at startup.
AdminServer was configured with hostname as Listen Address.
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