Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 PRADEEP CHOWDARY PYDI (PradeepPydi)
Anthem
Senior PEGA DEVOPS and Cloud Administrator
Anthem
US
PradeepPydi Member since 2017 240 posts
Anthem
Posted: Jan 25, 2019
Last activity: Jan 26, 2019
Posted: 25 Jan 2019 15:52 EST
Last activity: 26 Jan 2019 8:49 EST
Closed

AES connectivity issues.

Hi Andy/Jim,

SOAP service failure issues has been observed while monitored node trying to establish connection with AES.

(PRPC731,AES 731,Tomcat 8.5.32)

Please find below for the error in the logs.

2019-01-24 16:23:54,164 [ PegaRULES-Batch-1] [ STANDARD] [ ] [ PegaRULES:07.10] ( util.logging.SOAPAppenderPega) ERROR - AES-HEALTH-MSG : Exception in SOAPAppenderPega.sendEvent() Msg: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext) Cause: java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext).

PFA for the complete log.

To see attachments, please log in.
Pega Autonomic Event Services

Posted: 6 years ago
Posted: 26 Jan 2019 8:49 EST
PRADEEP CHOWDARY PYDI (PradeepPydi)
Anthem
Senior PEGA DEVOPS and Cloud Administrator
Anthem
US

Hi,

Tomcat 8.5.32.

"Can you please make sure SSL key location is correctly provided to App server"  Please provide additional details.

Thank you.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice