Weblogic Targets Begin Showing Down Status in Enterprise Manager Grid Control or Cloud Control
(Doc ID 2070444.1)
Last updated on NOVEMBER 16, 2022
Applies to:
Enterprise Manager for Fusion Middleware - Version 11.1.0.1 and laterInformation in this document applies to any platform.
Symptoms
EM 11g Grid Control begins reporting monitored WebLogic Server (WLS) domain members with a Down status, although these WLS instances are operating.
The <Agent Home>/sysman/log/emagent.trc file shows this, repeating:
2015-10-12 22:46:08,271 Thread-17140 ERROR fetchlets: oracle.sysman.emSDK.emd.fetchlet.FetchletException: oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException: Unhandled exception in lookup
2015-10-12 22:46:08,396 Thread-17140 ERROR engine: [oracle_repserv,/domain_domain/asinst_1/RptSvr_domain_asinst,Response] : nmeegd_GetMetricData failed : oracle.sysman.emSDK.emd.fetchlet.FetchletException: oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException: Unhandled exception in lookup
2015-10-12 22:46:08,396 Thread-17140 WARN collector: <nmecmc.c> Error exit. Error message: oracle.sysman.emSDK.emd.fetchlet.FetchletException: oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException: Unhandled exception in lookup
2015-10-12 22:46:08,396 Thread-17140 ERROR engine: [oracle_repserv,/domain_domain/asinst_1/RptSvr_domain_asinst,Response] : nmeegd_GetMetricData failed : oracle.sysman.emSDK.emd.fetchlet.FetchletException: oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException: Unhandled exception in lookup
2015-10-12 22:46:08,396 Thread-17140 WARN collector: <nmecmc.c> Error exit. Error message: oracle.sysman.emSDK.emd.fetchlet.FetchletException: oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException: Unhandled exception in lookup
also, from <Agent Home>/sysman/log/emagentfetchlet.trc:
2015-10-12 22:46:08,271 [nmefmgr_getJNIFetchlet] WARN emd.fetchlets getMetric.393 - oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException: Unhandled exception in lookup
oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException: Unhandled exception in lookup
at oracle.sysman.emd.fetchlets.JMX.generic.JMXFetchlet.getMetric(JMXFetchlet.java:199)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.sysman.emd.fetchlets.JMX.JMXFetchletWrapperBase.getMetric(JMXFetchletWrapperBase.java:99)
at oracle.sysman.emd.fetchlets.FetchletWrapper.getMetric(FetchletWrapper.java:382)
2015-10-12 22:46:09,285 [nmefmgr_getJNIFetchlet] WARN JMX.generic logp.251 - IOException: cannot communicate to Target with serviceURL=service:jmx:t3://hostname:9001/jndi/weblogic.management.mbeanservers.runtime for metric j2ee_application:Response_internal:: Unhandled exception in lookup Cause: javax.naming.NamingException: Unhandled exception in lookup [Root exception is org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: No]
oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException: Unhandled exception in lookup
at oracle.sysman.emd.fetchlets.JMX.generic.JMXFetchlet.getMetric(JMXFetchlet.java:199)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.sysman.emd.fetchlets.JMX.JMXFetchletWrapperBase.getMetric(JMXFetchletWrapperBase.java:99)
at oracle.sysman.emd.fetchlets.FetchletWrapper.getMetric(FetchletWrapper.java:382)
2015-10-12 22:46:09,285 [nmefmgr_getJNIFetchlet] WARN JMX.generic logp.251 - IOException: cannot communicate to Target with serviceURL=service:jmx:t3://hostname:9001/jndi/weblogic.management.mbeanservers.runtime for metric j2ee_application:Response_internal:: Unhandled exception in lookup Cause: javax.naming.NamingException: Unhandled exception in lookup [Root exception is org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: No]
This principle hods for EM 12c Cloud Control, also.
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 |
| References |