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-SOAP throws UnknownHostException



User has three source systems as 'A','B' & 'C' and each of these system hosts the web-service. User has reported inconsistent results on Rule-Connect-SOAP when trying to connect to these external web-services using the EndPoint URL. User has Data instance mapped to a Declare_Page that holds the information for each source system.

Error Messages

UserID - Unable to sendViaPost to url[]
    at com.pega.apache.commons.pega.PegaSSLProtocolSocketFactory.createSocket(
    at com.pega.apache.commons.httpclient.MultiThreadedHttpConnectionManager$
    at com.pega.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(
    at com.pega.apache.commons.httpclient.HttpMethodDirector.executeMethod(
    at com.pega.apache.commons.httpclient.HttpClient.executeMethod(
    at com.pega.apache.commons.httpclient.HttpClient.executeMethod(
    at com.pega.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(
    at com.pega.apache.axis2.transport.http.HTTPSender.sendViaPost(
    at com.pega.apache.axis2.transport.http.HTTPSender.send(
    at com.pega.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(
    at com.pega.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(
    at com.pega.apache.axis2.engine.AxisEngine.send(
    at com.pega.apache.axis2.description.OutInAxisOperationClient.send(
    at com.pega.apache.axis2.description.OutInAxisOperationClient.executeImpl(
    at com.pega.apache.axis2.client.OperationClient.execute(
    at com.pegarules.generated.activity.ra_action_invokeaxis2_7085a8222e313309ee4c4642bb83bcde.step14_circum0(
    at com.pegarules.generated.activity.ra_action_invokeaxis2_7085a8222e313309ee4c4642bb83bcde.perform(
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
    at com.pegarules.generated.activity.ra_action_invoke_d7dd9a2f387cb620a38d17a76368e747.step8_circum0(
    at com.pegarules.generated.activity.ra_action_invoke_d7dd9a2f387cb620a38d17a76368e747.perform(
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(

Steps to Reproduce


Root Cause

The service end point URL belonging to System ‘A’ does not work consistently due to network/DNS configuration issues.


Using IP address in the service end point URL instead of using hostname+domain name has helped resolve the issue.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% 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