Support Article

AES not able to monitor nodes running on JBOSS

SA-25004

Summary



User completed the configuration of Autonomic Event Services (AES) 7.1.7 on Pega 7.2. User was unable to monitor any nodes as Nodes were not sending the data to AES system due to the SSL handshake issue.

Error Messages



2016-06-17 15:00:01,195 ERROR [stderr] (Dispatcher-Thread-106) log4j:ERROR Msg: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
2016-06-17 15:00:01,195 ERROR [stderr] (Dispatcher-Thread-106) log4j:ERROR Cause: com.ctc.wstx.exc.WstxIOException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
2016-06-17 15:00:02,054 ERROR [stderr] (Dispatcher-Thread-106) log4j:ERROR Exception in SOAPAppenderPega.sendEvent()
2016-06-17 15:00:02,054 ERROR [stderr] (Dispatcher-Thread-106) log4j:ERROR Msg: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
2016-06-17 15:00:02,054 ERROR [stderr] (Dispatcher-Thread-106) log4j:ERROR Cause: com.ctc.wstx.exc.WstxIOException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure


Steps to Reproduce



Install AES 7.1.7 on PRPC 7.2 and try to monitor other Pega7 applications running on JBOSS 6.x server.


Root Cause



When a monitored node is running on JBoss instance and because of specific management interface implementation in JBoss, the PRPC server is unable to retrieve the required MBeans during the server startup. The Mbeans contains the attributes necessary to automatically establish the connection between the AES Server and the Monitored node.



Resolution



User was facing SSL handshake exception while connecting to the monitored node server.
GCS personnel suggested the user to redeploy key store and trust store certificates to resolve SSL issue. Once this issue is resolved they can manually update the Connection String of the monitored nodes in PegaAES-Data-Nodes instance.

Refer to following PDN articles which helps us on how to update the Connection String manually:

https://pdn.pega.com/support-articles/soap-errors-aes-monitored-node
https://pdn.pega.com/troubleshooting-autonomic-event-services-aes-enterprise-edition-configuration-and-installation

Note : This manual process is only required for monitored nodes that are running on JBoss instances.

Published June 28, 2016 - Updated August 23, 2017

Have a question? Get answers now.

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