Support Article

(404)Not Found errors in AES log file

SA-51687

Summary



readFromSocket errors in log file when Autonomic Event Services (AES) is trying to get information from monitored nodes.

Error Messages


In one case a 404 is indicating the node may not exist or is not reachable from AES

Caused by:
(404)Not Found
at com.pega.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:744)
at com.pega.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
at com.pega.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at com.pega.apache.axis.SimpleChain.doVisiting(SimpleChain.java:119)
at com.pega.apache.axis.SimpleChain.invoke(SimpleChain.java:84)

In another case the node has not self recognized it's URL.

java.net.MalformedURLException: no protocol: [unable to determine]
at java.net.URL.<init>(URL.java:609)
at java.net.URL.<init>(URL.java:506)
at java.net.URL.<init>(URL.java:455)
at com.pega.apache.axis.client.Call.<init>(Call.java:339)


Steps to Reproduce



Not applicable

Root Cause



A defect or configuration issue in the operating environment:

In the case of a 404 when AES is attempting to research rules or 'pull' from the monitored node, this indicates the node is down or not reachable from AES server.

This does not mean that the monitored node cannot talk to the AES server and send alerts and health messages. It is not the case that the connection is always reciprocal.

In the case of the MalformedURLException, the monitored node has been unable to determine it's own URL and has sent the string [unable to determine] to the AES server. This happens in various environments on startup of the monitored nodes for a variety of reasons. The URL is sent at startup in a PEGA0008 alert. AES server will create a cluster and node using the details provided in the PEGA0008 alert, only if they do not already exist.


Resolution



Make the following change to the operating environment:

In the first case (404) consult with the infrastructure team at your site to determine if the monitored node can be made reachable from the AES server. If not, then you can use the AES System Settings to disable the pull features and suppress the errors.


In the second case the URL in the New Connection string of the AES node needs to be updated.

Published February 8, 2018 - Updated February 26, 2018

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.