News
Perth, Australia
+ (61) 417713124
prosolutions@gavinsoorma.com

1 Comments

gjorgjiz96802300
  • Oct 4 2018
Hello Gavin, This is Kent. I work with Gjorgji at Paymentus. We're testing GoldenGate, and followed your great instruction installed GoldenGate Monitoring Agent 12.2.1.2.0 to monitor GoldenGate 12.3.0.1 with EM 13c. However, when we started JAGENT from ggsci, we saw following error in OGG Agent log gg_agent.log, [root@site3-rac1 logs]# more ogg_agent.log [2018-10-02T16:42:38.086-04:00] [JAGENT] [ERROR] [OGGMON-20609] [com.goldengate.monitor.jagent.comm.ws.ManagerService] [tid: MessageCollector] [ecid: 0000MOqXBAuD^aWFLzATOA1RgxWy000002,0] Unsuccessful connection respon se from Message Web Service. Query String: messages/last ; Response Code: 404 ; Response Message: Not Found [2018-10-02T16:42:38.149-04:00] [JAGENT] [ERROR] [OGGMON-20603] [com.goldengate.monitor.jagent.comm.ws.ManagerService] [tid: MessageCollector] [ecid: 0000MOqXBAuD^aWFLzATOA1RgxWy000002,0] RESTful Web Service with name messages/last has become unresponsive [2018-10-02T16:42:38.101-04:00] [JAGENT] [ERROR] [OGGMON-20494] [com.goldengate.monitor.jagent.comm.ws.NotificationsCollector] [tid: StatusCollector] [ecid: 0000MOqXBAtD^aWFLzATOA1RgxWy000001,0] Error occurred while re gistering the OGG process. Exception: [[ source parameter must not be null ]] [2018-10-02T16:42:38.152-04:00] [JAGENT] [ERROR] [OGGMON-20609] [com.goldengate.monitor.jagent.comm.ws.ManagerService] [tid: MessageCollector] [ecid: 0000MOqXBAuD^aWFLzATOA1RgxWy000002,0] Unsuccessful connection respon se from Message Web Service. Query String: messages/last ; Response Code: 404 ; Response Message: Not Found [2018-10-02T16:42:38.152-04:00] [JAGENT] [ERROR] [OGGMON-20603] [com.goldengate.monitor.jagent.comm.ws.ManagerService] [tid: MessageCollector] [ecid: 0000MOqXBAuD^aWFLzATOA1RgxWy000002,0] RESTful Web Service with name messages/last has become unresponsive [2018-10-02T16:42:42.881-04:00] [JAGENT] [ERROR] [OGGMON-20366] [com.goldengate.monitor.jagent.comm.ws.ManagerWSAdapter] [tid: getInstanceList] [ecid: 0000MOqXCL1D^aWFLzATOA1RgxWy000003,0] Could not get WSInstance Info rmation , [[ com.goldengate.monitor.model.AgentCommunicationException: Failed to get Registry. at com.goldengate.monitor.jagent.comm.ws.ManagerWSApi.getInstanceInfo(ManagerWSApi.java:239) at com.goldengate.monitor.jagent.comm.ws.ManagerWSAdapter.getInstanceInfoNative(ManagerWSAdapter.java:105) at com.goldengate.monitor.jagent.comm.impl.ManagerFacadeImpl.fillInstanceMap(ManagerFacadeImpl.java:259) at com.goldengate.monitor.jagent.comm.impl.ManagerFacadeImpl.getInstances(ManagerFacadeImpl.java:253) at com.goldengate.monitor.jagent.jmx.MBeansContainerImpl.createMBeans(MBeansContainerImpl.java:344) at com.goldengate.monitor.jagent.jmx.MBeansContainerImpl$1.run(MBeansContainerImpl.java:836) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalArgumentException: source parameter must not be null at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:119) at com.sun.xml.internal.ws.message.AbstractMessageImpl.readPayloadAsJAXB(AbstractMessageImpl.java:135) at com.sun.xml.internal.ws.api.message.MessageWrapper.readPayloadAsJAXB(MessageWrapper.java:171) at com.sun.xml.internal.ws.client.dispatch.JAXBDispatch.toReturnValue(JAXBDispatch.java:88) at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:274) at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:289) at com.goldengate.monitor.jagent.comm.ws.ManagerService.getRegistry(ManagerService.java:267) at com.goldengate.monitor.jagent.comm.ws.ManagerWSApi.getInstanceInfo(ManagerWSApi.java:230) ... 6 more ]] [2018-10-02T16:42:42.882-04:00] [JAGENT] [ERROR] [OGGMON-20352] [com.goldengate.monitor.jagent.comm.impl.ManagerFacadeImpl] [tid: getInstanceList] [ecid: 0000MOqXCL1D^aWFLzATOA1RgxWy000003,0] Instance List returned fro m JNI call is null After search MOS, we found it matches with this Doc, Oracle GoldenGate Monitor Agent on Windows Platforms receive OGGMON-20609 Unsuccessful connection response from Message Web Service Query String: messages/last ; Response Code: 404 ( Doc ID 2199889.1 ) Per doc, this issue is caused by Bug 23285087 - OGGMON-20609 Query String: messages/last Code: 404 ; Response Message: Not Found. And it has been fixed in Oracle GoldenGate Monitor Agent (formerly jagent) 12.2.1.2.0, which is the version we're using. Just want check whether you have seen this issue before, or any idea it could be fixed. Thanks, Kent

Leave Reply

Your email address will not be published. Required fields are marked *