Skip to Main Content

Enterprise Manager

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

OEM11g sees WebLogic 10.3.3.0 AdminServer, NOT other WL server instances

874729Jul 11 2011 — edited Feb 20 2012
My organization is running OEM Grid Control 11g on a RHEL server monitoring WebLogic 10.3.3.0 servers running on Windows Server 2003. All OS's, apps, agents, etc are fully patched.

The WL servers are configured with the AdminServer and one application server on a host, another host with a secondary application server deployed, and another host with jRules deployed. OEM sees all the hosts, servers and applications, but it doesn't report all as up.

On Host1 OEM reports the host is up, the AdminServer as up, but it reports the AppServer1 and the application deployments are down.

On Host2 OEM reports the host is up but all servers and application deployments are down.

On Host3 OEM reports the host is up but all servers and application deployments are down.

The AdminServer is set up to communicate in the clear, the AppServers are set up to communicate (with an Apache server) SSL. The AdminServer sees the AppServers and the application deployments correctly.

I get the following errors in the agent log:

+2011-07-08 16:28:57,353 [nmefmgr_getJNIFetchlet] WARN JMX.generic logp.251 - IOException: cannot communicate to Target with serviceURL=service:jmx:t3s://*FQDN*:7002/jndi/weblogic.management.mbeanservers.runtime for metric weblogic_j2eeserver:server_internal:: Couldn't connect to any host Cause: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]+


+2011-07-08 16:29:48,344 [nmefmgr_getJNIFetchlet] WARN JMX.generic logp.251 - IOException: cannot communicate to Target with serviceURL=service:jmx:t3://0.0.0.0:7001/jndi/weblogic.management.mbeanservers.runtime for metric weblogic_j2eeserver:server_internal:: Couldn't connect to any host Cause: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]+

I'm not sure why I get the 0.0.0.0, I have the listen address set in the WL console.

Any help is appreciated. If you need any more info I'll be glad to supply.
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 19 2012
Added on Jul 11 2011
2 comments
284 views