My Oracle Support Banner

EM13c: OHS Target Response Metric Collection Time Out When Configured With mod_proxy_ajp Module (Doc ID 2636597.1)

Last updated on APRIL 01, 2020

Applies to:

Enterprise Manager for Fusion Middleware - Version and later
Information in this document applies to any platform.


EM 13c
Agent Version :
OMS Version   :
OHS Version   :

Four instances of HTTP standalone servers have been added to OEM monitoring and the targets were added using guided process of discovery.
Metric evaluation error alert is seen for 2 of the instances. This alert happens several times a day and is cleared almost immediately after sending the alert.

Metric evaluation error start - oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: Timeout during collection: oracle.sysman.gcagent.task.TaskTimeoutException: task timeout: 120000 MILLISECONDS for oracle_apache:<INSTANCE NAME>_ohs1:Response

OHS log has below error captured:
[2020-01-14T09:42:44.5044+02:00] [OHS] [ERROR:32] [] [core.c] [host_id: <HOST_ID>] [host_addr: <IP ADDRESS>] [tid: 140031461074688] [user: fmwadmin] [ecid: 005b1IpE3OY6iKyaw5jc6G0005H90000NR] [rid: 0:1] [VirtualHost: localhost:10853] proxy: AJP: failed to make connection to backend: <HOSTNAME>


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

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