Pega AES node integration failing
Hi,
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.
Kindly help.
Thanks!
***Edited by Moderator Marissa to update platform capability tags****
British Telecom
IN
Hi,
You can have a look at below link:
Seems like issue with JDK/JRE version.
Pegasystems Inc.
US
What Pega version?
What java version(s)?
Which app server?
What URL are you using? Are you entering the URL in System / Settings / PDC or trying some other form of configuration?
Where do you see the exception?
Cognizant
IN
Pega Verion - 7.2.2
Java Version - 1.8
java version "1.8.0_181"
Java(TM) SE Runtime Environment (build Proprietary information hidden - pxa6480sr5fp21-20180830_01(SR5 FP21))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20180829_395745 (JIT enabled, AOT enabled)
OpenJ9 - e82188c
OMR - eeaa30e
IBM - 98805ca)
JCL - 20180821_01 based on Oracle jdk8u181-b12
AES Appserver - 7.2.2
By using the PDC given the Pega soap URL(https://hostname:9xxx/prweb/PRSOAPServlet) and the test connection is successful, however node is not visible at AES monitoring server
Pegasystems Inc.
US
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
Cognizant
IN
Hi Werda,
Thanks for your update, I have did the below analysis and as suggested I have enabled the debug mode and I can see the below warning exceptions on the log,
[2/20/19 23:52:16:182 EST] 000052ee com.ibm.ws.session.WASSessionCore W Detected JSESSIONID with invalid length; expected length of 23, found 28, setting: 2D83822B44388421710C4E9CD289 to null.
[2/20/19 23:52:16:729 EST] 000052f8 com.ibm.ws.session.WASSessionCore
[2/20/19 23:41:22:035 EST] 0000018a SystemOut O CipherBox: Using cipher AES/GCM/NoPadding from provider from init IBMJCE version 1.8
[2/20/19 23:41:22:036 EST] 0000018a SystemOut O PegaRULES-Batch-5, WRITE: TLSv1.2 Alert, length = 26
[2/20/19 23:41:22:036 EST] 0000018a SystemOut O PegaRULES-Batch-5, called closeSocket(true)
Hi Werda,
Thanks for your update, I have did the below analysis and as suggested I have enabled the debug mode and I can see the below warning exceptions on the log,
[2/20/19 23:52:16:182 EST] 000052ee com.ibm.ws.session.WASSessionCore W Detected JSESSIONID with invalid length; expected length of 23, found 28, setting: 2D83822B44388421710C4E9CD289 to null.
[2/20/19 23:52:16:729 EST] 000052f8 com.ibm.ws.session.WASSessionCore
[2/20/19 23:41:22:035 EST] 0000018a SystemOut O CipherBox: Using cipher AES/GCM/NoPadding from provider from init IBMJCE version 1.8
[2/20/19 23:41:22:036 EST] 0000018a SystemOut O PegaRULES-Batch-5, WRITE: TLSv1.2 Alert, length = 26
[2/20/19 23:41:22:036 EST] 0000018a SystemOut O PegaRULES-Batch-5, called closeSocket(true)
[2/20/19 23:41:22:050 EST] 0000018a SystemOut O
Is initial handshake: true
[2/20/19 23:41:22:051 EST] 0000018a SystemOut O %% Client cached [Session-31219, SSL_RSA_WITH_AES_256_GCM_SHA384]
[2/20/19 23:41:22:051 EST] 0000018a SystemOut O ALPNJSSEExt protocol not set for Client
[2/20/19 23:41:22:051 EST] 0000018a SystemOut O *** ClientHello, TLSv1.2
[2/20/19 23:41:22:051 EST] 0000018a SystemOut O RandomCookie:
[2/20/19 23:41:22:051 EST] 0000018a SystemOut O GMT: 1550723826
Note :-Soap connection works fine from AES server to Node but from Node to AES server its not working and can see the above exception on the log file.a
Pegasystems Inc.
US
where's the pegarules log? I don't see any entries for httpclient.* in the posting above - these look like websphere debug messages from systemout/systemerr.
Cognizant
IN
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 ?
Pls suggest.
Pegasystems Inc.
US
what platform version is this?
best collect what data is sent to PDC. Enable debug for classes httpclient.wire.header, httpclient.wire.contenat and any class that is named SoapAppender*