My Oracle Support Banner

Monitoring Apache Tomcat Server Fails With Metric Collection Error when Tomcat is Down (Doc ID 889675.1)

Last updated on APRIL 01, 2022

Applies to:

Enterprise Manager for Miscellaneous Plug-ins - Version 1.0 to 1.0
Information in this document applies to any platform.
Applies to version 1.0.3.0.0 (release 6) of the Tomcat plug-in

 

Symptoms

Let us consider the case of Grid Control 10.2.0.5 monitoring Apache Tomcat using the Apache Tomcat plugin.

When Tomcat is up, Grid Control reports the availability of the Tomcat target as up.
However, when Tomcat is down, Grid Control reports a Metric Collection Error for the Tomcat target, instead of showing it down.

Here's an example of that collection error:

Target: MatTomcat
Type: Apache Tomcat
Metric: Response
Collection Timestamp: Sep 18, 2009 4:18:16 PM
Error Type: Collection Failure
Message: oracle.sysman.emSDK.emd.fetchlet.FetchletException: oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: <hostname.domain>; nested exception is: java.net.ConnectException: Connection refused]


The $AGENT_HOME/sysman/log/emagent.trc has the following entries:

<Timestamp> Thread-2872040352 ERROR engine:
[tomcat,MatTomcat,Response] : nmeegd_GetMetricData failed :
oracle.sysman.emSDK.emd.fetchlet.FetchletException:
oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException:
Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException
[Root exception is java.rmi.ConnectException: Connection refused to host:
<hostname.domain>; nested exception is: java.net.ConnectException:
Connection refused]


The $AGENT_HOME/sysman/log/emagentfetchlet.trc has the following entries:

<Timestamp> [nmefmgr_getJNIFetchlet] ERROR JMX.generic logp.251 - Error: cannot communication with Target
java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException
[Root exception is java.rmi.ConnectException: Connection refused to host: <hostname.domain>; nested exception is:
java.net.ConnectException: Connection refused]
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:317)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at oracle.sysman.emd.fetchlets.JMX.generic.JMXContext.connectJVM(JMXContext.java:708)
at oracle.sysman.emd.fetchlets.JMX.generic.JMXContext.connect(JMXContext.java:617)
at oracle.sysman.emd.fetchlets.JMX.generic.JMXFetchlet.getMetric(JMXFetchlet.java:111)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at oracle.sysman.emd.fetchlets.JMX.JMXFetchletWrapperBase.getMetric(JMXFetchletWrapperBase.java:92)
at oracle.sysman.emd.fetchlets.FetchletWrapper.getMetric(FetchletWrapper.java:382)

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
Cause
Solution
References

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