Integration Gateway: No response received from Gateway (158,10829)

by Apurva Tripathi on July 9, 2013

in PeopleSoft Integration Broker

This error is applicable for PeopleTools 8.4x and 8.5x and is one of the most common Integration Broker issue. When trying to ping the node, or send to it a message results in the following error:

No response received from Gateway. The Gateway did not send back a IBResponse


Integration Gateway: No response received from Gateway (158,10829)

The log shows something like this HttpTargetConnector:ExternalSystemContactException Connection reset
at javax.servlet.http.HttpServlet.service(

There are several probable causes of this:

The problem is caused by a failed connection between the application server and the gateway web server. This is typically associated with integration setup problem and the common ones are:

  • Incorrect setup
  • Proxy server setup or firewall rule issue
  • /etc/hosts file entries on unix application servers
  • Load Balancer setup issues

Some of the obvious solutions are

1) First and foremost – check your integration broker settings:

– Ensure that you can ping the Gateway

– Ensure that you can ping the default local node

– Ensure that you can ping the nodes defined in the Gateway properties.

Sometimes even a small typo like incorrect server address or port # could result in this error.

2) Proxy server setup
-Ensure that the proxy device has the correct entries listed
-Ensure that the Peoplesoft system is pointing to the correct proxy server in each configuration file

3) /etc/hosts file entries on unix application servers
-Check the Peoplesoft application server /etc/hosts file for invalid machine name or port entries.
-Verify that the application server configuration works with the machine name listed for the JOLT server name entry rather than %PS_MACH% and use the same entry in the file as that specified in the psappsrv.cfg file

Also Read:  How to reset the administrator login password for accessing to the IB gateway advanced setup page?

4) Load Balancer setup issues
– Ensure that the load balance device is pointing to the correct physical machine name/ip address

5) Firewall blockages
– If a firewall exists between systems, ensure that both the gateway and application server machine ports are open for 2 way communication

ThisĀ  error is also caused by the error “Cannot establish HTTP connection (158, 2842)“. Refer to the URL for resolution of the same.

{ 5 comments… read them below or add one }

mahmoodq1 September 9, 2013 at 9:38 am

Apurva, I am getting the following error when I am try to consume a web service. Do you what it could be?
Integration Gateway – External System Contact Error (158,10721)


Prashant September 9, 2013 at 9:26 pm

Hi, There could be several reasons for this error. I would suggest checking errorlog for IB gateway placed in webserver PSIGW directory. Check if you are able to open the WSDL directly in a browser. If yes, then it’s something related to IB configuration at your end otherwise the target system may be down.

Let us know what you find.


Subhiksh Divakaran February 28, 2016 at 12:05 pm

Apurva, I am using REST based web service as a medium to consume third party. Actually, i have to request for an access key from the third party using the post url that they render. I tested it with SOAP UI tool and i am getting the desired response. But when i try it by creating REST based webservice i get error like “External system contact error”. I checked the default node and gateway and both are pinging successfully, but the portal nodes for e.g. EMPL gives error : Unable to decrypt password. Although i am using 8.54 Peopletools to develop REST, is there an issue with using 8,53 for the same?
It would be great if you could help me out.


harshitha August 8, 2017 at 4:52 am

Hi Subhiksh

I am facing the same problem – Unable to decrypt the password when i ping the external node which has third party url
How did you solve your problem?


Apurva T. August 21, 2017 at 10:14 am

Check your integration broker gateways properties file and look for appserver domain passwordds and secure keystore password.


Cancel reply

Leave a Comment

Previous post:

Next post: