My Oracle Support Banner

EM 11G WebLogic Components (Admin, Managed servers in GCDomain) won't start, errors re: JMX Connectivity (Doc ID 1308550.1)

Last updated on MARCH 26, 2021

Applies to:

Enterprise Manager Base Platform - Version 11.1.0.1 to 11.1.0.1 [Release 11.1]
Information in this document applies to any platform.
Affects Enterprise Manager 11G release



Symptoms

 

Note : This problem can manifest in a number of ways.  If even one of the below symptoms is a match for something you are seeing in the environment, take corrective action; make sure the administration-port is not enabled for the domain as per the solution in this doucument


Symptom 1

Starting the Enterprise Manager service results in output such as:

./emctl start oms
Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Starting WebTier...
WebTier Successfully Started
Starting Oracle Management Server...
Oracle Management Server Could Not Be Started
Oracle Management Server is Down
Please check <EM_INSTANCE_HOME>/em/EMGC_OMS1/sysman/log/emctl.log for error details


The administration server (https://<OMS_HOSTNAME>:<EM_CONSOLE_PORT>/console) never comes up properly and the URL is inaccessible.

Symptom 2

The Admin server logs show something like :

<EM_INSTANCE_HOME>/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.log

 

####<Mar 29, 2011 1:24:01 PM EDT> <Info> <JMX> <omshost.com> <EMGC_ADMINSERVER> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1301419441688> <BEA-149506> <Established JMX Connectivity with EMGC_OMS1 at the JMX Service URL of service:jmx:admin://<OMS_HOSTNAME>:<EM_CONSOLE_PORT>/jndi/weblogic.management.mbeanservers.runtime.>
####<Mar 29, 2011 1:24:04 PM EDT> <Info> <Server> <omshost.com> <EMGC_ADMINSERVER> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1301419444322> <BEA-002634> <The server "EMGC_OMS1" disconnected from this server.>


The administration server on 9002 port comes up fine (https://<OMS_HOSTNAME>:<EM_CONSOLE_PORT>/console) comes up properly as the port is changed from default 7101 to 9002

In some rare cases, the Admin server may crash altogether when starting up the services.  In this case, the above message would not even get printed into the log because the admin server would immediately crash instead.

Symptom 3

The Managed server logs show

<EM_INSTANCE_HOME>/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out



<Mar 29, 2011 1:24:03 PM EDT> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "DefaultAdministration". The address <IP_ADDRESS> might be incorrect or another process is using port <EM_CONSOLE_PORT>: java.net.BindException: Address already in use.>
<Mar 29, 2011 1:24:03 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: Failed to start admin channel DefaultAdministration[admin]>


This is a sure sign the administration port has been enabled for the domain.  Take the corrective action as documented below.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
 Scenario 1: Admin port changed un-intentionally
 Scenario 2: Admin port changed intentionally


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.