Posted: 19 Nov 2018 12:54 EST Last activity: 1 Mar 2019 16:06 EST
Pega AES node integration failing
I have installed the AES on our new server and trying to add the dev node by using End point soap service url but its getting failed with below error,
[err] log4j:ERROR SOAPAppender _append() failed: java.lang.IllegalArgumentException: The XMLInputFactory does not recognize the property "reuse-instance".
[err] java.lang.IllegalArgumentException: The XMLInputFactory does not recognize the property "reuse-instance".
[err] at com.ibm.xml.xlxp.api.stax.msg.StAXMessageProvider.throwIllegalArgumentException(StAXMessageProvider.java:42)
However I am able to add the UAT node without any issues.
***Edited by Moderator Marissa to update platform capability tags****
Start by enabling debugging on monitored node - set logging level of httpclient.wire.content and wire.header to DEBUG. That will show every message sent to AES server. Validate that messages are being sent and processed
Within AES check that all agents are running on all nodes; look at classes pegaaes-data-node, pegaaes-data-cluster, pegaaes-data-nodestats, etc ... see if you are receiving and storing data correctly
Good news, issue resolved after configuring the static clone ID on the application server, we can see the nodes on AES server.
I have changed the System Name on Pega monitored node and deleted the exiting node from the AES server but again the node is not coming in to the AES Server...do we needs to do any changes on AES/Node box after the system name changes?
I have reverted the System name changes from other customized name to pega then it started work again and I could see the monitored node on the AES server.
So if we have change the default system name from pega to anyother name, monitored node is not visible at AES server, after changing the default system name from the monitored node, do we needs to do any config changes to connect the monitored with AES server ?