Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Connect REST not able to receive response from Service

SA-43279

Summary



Connect REST not able to receive response from Service. The NAT IPs has been opened for this Cloud Instance to connect with CVS Network REST Services.

But after doing that change, when a Connect REST was configured to invoke REST Services, exception was found in Test Connectivity. The exception has been noticed while test connectivity as well invocation.

Error Messages



2017-08-17 15:14:59,217 [tp-bio-8443-exec-162] [TABTHREAD1] [ VDEApp:01.01.01] (ivity.Rule_Connect_REST.Action) ERROR <IP1>|<IP2> Z205746 - Exception caught during REST Connector connectivity test
java.lang.Exception: Secure Socket Factory is unable to create a socket. Check Secure protocol configuration of Connector.
at com.pegarules.generated.activity.ra_action_pytestconnectivity_4ae2e509317e3da3df03327ee09c56f0.step4_circum0(ra_action_pytestconnectivity_4ae2e509317e3da3df03327ee09c56f0.java:646)
...
2017-08-18 13:59:51,724 [ PegaRULES-Batch-1] [ STANDARD] [ EMA:01.07.01] (FW_EMAFW_Work_Exception.Action) INFO - ProcessBatchTask Started
2017-08-18 14:00:02,989 [ttp-bio-8443-exec-38] [ STANDARD] [ VDEApp:01.01.01] (ector.Rule_Connect_REST.Action) ERROR Z205746 - com.pega.pegarules.pub.PRRuntimeException: Cannot create Secure Socket - no protocols available
2017-08-18 14:00:02,990 [ttp-bio-8443-exec-38] [ STANDARD] [ VDEApp:01.01.01] ( internal.mgmt.Executable) ERROR Z205746 - Exception
com.pega.pegarules.pub.services.ConnectorException: Caught unhandled exception: com.pega.pegarules.pub.PRRuntimeException: Cannot create Secure Socket - no protocols available

Steps to Reproduce

  1. Configure a Connect REST rule.
  2. Try Test Connectivity from the Connect rule or Invoke the Connector from Data Page. TLS 1.2 used.

Root Cause



A defect or configuration issue in the operating environment:

The endpoint was enabled only for TLS 1.2 and Pega application server was using JAVA 1.6 which doesn't support TLS 1.2.

Resolution



Upgrade to Java 1.7 or above.

Published December 5, 2017 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us