Support Article
IllegalStateException: Target host must not be null
SA-7997
Summary
You have an activity that calls a Connect-Rest Rule which in turn invokes a REST service over https. This fails with an error. The error can be observed in the PegaRULES log file.
WebSphere is configured to use a custom TrustStore.
Error Messages
[3/23/15 14:32:18:098 EDT] 00000088 stdout Z 2015-03-23 14:32:18,097 [ WebContainer : 5] [ STANDARD] [IssuerPEGA:01.01.01] (ector.Rule_Connect_REST.Action) ERROR <HOST> - Caught unhandled exception: java.lang.IllegalStateException: Target host must not be null, or set in parameters.
java.lang.IllegalStateException: Target host must not be null, or set in parameters.
at com.pega.apache.http.impl.client.DefaultRequestDirector.determineRoute(DefaultRequestDirector.java:717)
at com.pega.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:358)
at com.pega.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at com.pega.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_df52818cef8298fb6efc6d2a51806775.step5_circum0(ra_action_pyinvokerestconnector_df52818cef8298fb6efc6d2a51806775.java:1144)
///
Caused by:
java.lang.IllegalStateException: Target host must not be null, or set in parameters.
at com.pega.apache.http.impl.client.DefaultRequestDirector.deter
[3/23/15 14:32:18:100 EDT] 00000088 stdout Z mineRoute(DefaultRequestDirector.java:717)
at com.pega.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:358)
at com.pega.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at com.pega.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_df52818cef8298fb6efc6d2a51806775.step5_circum0(ra_action_pyinvokerestconnector_df52818cef8298fb6efc6d2a51806775.java:1144)
Steps to Reproduce
Not Applicable
Root Cause
The root cause of this problem is defect/misconfiguration in the PRPC 6.3 SP1 operating environment. Connect-REST calls in PRPC 6.3 SP1 use the default JVM trust store, cacerts. Hence, the appropriate trusted certs and root certs need to be installed in JVM's cacerts trustStore found in jre/lib/security folder.
Resolution
Update the default JVM trust store in jre/lib/security folder (cacerts) with appropriate trusted certs and root certs for successful SSL communication.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.