How To Fix Jagent Logs Filling Up With XML-20221: (Fatal Error) Invalid Char In Text.] Errors? (Doc ID 2172281.1)

Last updated on NOVEMBER 03, 2016

Applies to:

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

Goal

How to Fix OGG Monitor Agent (formerly jagent) log filling up with XML-20221: (Fatal Error) Invalid char in text.] errors ?

If ogg_agent.log is filling up quickly with

[JAGENT] [ERROR] [OGGMON-20603] [com.goldengate.monitor.jagent.comm.ws.ManagerService] [tid: MessageCollector]
[JAGENT] [ERROR] [OGGMON-20612] [com.goldengate.monitor.jagent.comm.ws.ManagerService] [tid: MessageCollector]

javax.xml.bind.UnmarshalException
- with linked exception:
[org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 24654; : XML-20221: (Fatal Error) Invalid char in text.]
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalException(AbstractUnmarshallerImpl.java:335)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.createUnmarshalException(UnmarshallerImpl.java:503)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:204)

type errors follow the steps provided below to fix this issue.
 

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