Support Article
Monitored node URL [unable to determine]
SA-26498
Summary
There are two nodes that report their URL to Autonomic Event Services (AES) as [unable to determine]. These need to be remedied.
The nodes are c60bd1759b4ab41a6c0e218a26a0b1ee and a3b074b3841727432130126d31707d1a. Need to replace the connection string with the correct URL.
Error Messages
ERROR Rule-Connect-SOAP.PegaAES-Data-RSSnapshot.GetRuleSetSnapshot - Exception
com.pega.pegarules.pub.services.ConnectorException: Service URL '[unable to determine]' value is invalid
at com.pegarules.generated.activity.ra_action_invokeaxis_3d1646543ec549a24978e7db117c3cd5.step2_circum0(ra_action_invokeaxis_3d1646543ec549a24978e7db117c3cd5.java:612)
at com.pegarules.generated.activity.ra_action_invokeaxis_3d1646543ec549a24978e7db117c3cd5.perform(ra_action_invokeaxis_3d1646543ec549a24978e7db117c3cd5.java:86)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3505)
...
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.MalformedURLException: no protocol: [unable to determine]
at java.net.URL.<init>(URL.java:585)
at java.net.URL.<init>(URL.java:482)
at java.net.URL.<init>(URL.java:431)
at com.pega.apache.axis.client.Call.<init>(Call.java:339)
at com.pegarules.generated.activity.ra_action_invokeaxis_3d1646543ec549a24978e7db117c3cd5.step2_circum0(ra_action_invokeaxis_3d1646543ec549a24978e7db117c3cd5.java:607)
Steps to Reproduce
Not Applicable
Root Cause
A defect in Pegasystems’ code or rules. Initialization of the monitored node is such that the introspection for the URL cannot be done.
Resolution
Read the following SA for recommendation:
SA-17895 - Monitored Node on JBoss instances does not connect to AES Server.
Published August 23, 2017 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.