Support Article
SOAP errors on AES-monitored node
SA-7393
Summary
SOAP errors are being seen on AES-monitored node. Monitored Node is not sending AES Alert events.
This began occurring after upgrading from 7.1.5 to 7.1.7
Error Messages
2015-03-02 15:19:53,348 ERROR [STDERR] (Dispatcher-Thread-21) log4j:ERROR Exception in SOAPAppenderPega.sendEvent()
2015-03-02 15:19:53,348 ERROR [STDERR] (Dispatcher-Thread-21) log4j:ERROR Msg: (304)Not Modified
2015-03-02 15:19:53,348 ERROR [STDERR] (Dispatcher-Thread-21) log4j:ERROR Cause: null
Root Cause
The root cause of this problem is a misconfiguration in the PRPC operating environment. SOAP URL connection string in the PegaAES-Data-Nodes instance was incorrectly configured.
Resolution
This issue is resolved through the following local change: Updated the SOAP url connection string in the PegaAES-Data-Nodes instance to the correct one.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.