OGG Monitoring Checklist - Debugging Items Needed For OGGMON-20603 OGGMON-20610 RESTful Web Service with name messages/last has become unresponsive (Doc ID 2158637.1)

Last updated on JANUARY 30, 2017

Applies to:

Oracle GoldenGate - Version 11.2.1.0.22 and later
Management Pack for Oracle GoldenGate - Version 11.1.1.0.50 and later
Information in this document applies to any platform.

Goal

The goal of this document is to list the items commonly required by support engineers and development when debugging GoldenGate Monitoring issues.

This guide is targeted towards debugging the following errors

[JAGENT] [ERROR] [OGGMON-20603] [com.goldengate.monitor.jagent.comm.ws.ManagerService] [tid: MessageCollector] [ecid:0000LFzpBN83b6rpsGT4iX1N2Z9I000004,0] RESTful Web Service with name messages/last has become unresponsive

[JAGENT] [ERROR] [OGGMON-20610] [com.goldengate.monitor.jagent.comm.ws.ManagerService] [tid: MessageCollector] [ecid:0000LFzpBN83b6rpsGT4iX1N2Z9I000004,0] Could not connect to Message Web Service. Query String: messages/last

found in $OGG_AGENT_INST_HOME/logs/ogg_agent.log

The information gathered from these items can also help debug other common monitoring issues such as:

- GoldenGate Targets not getting discovered in OEM 12c
- Jagent immediately stops after start from ggsci prompt
- GoldenGate promoted targets in OEM 12c are out of sync status when compared against "info all" command in ggsci prompt
- GoldenGate promoted targets in OEM 12c show stale/old metrics data such as Lag (sec), Last Checkpoint Timestamp, ETC
- 'datastore' type errors in ggserr.log

 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms