502 Bad Gateway error

[Former Member]

Hello,

We are doing performance testing in our testing for SOAP to Proxy call.

We are using Webserver and webserver will forward the request to SAP PI application server for SOAP call.

While doing performance testing for 500 requests, what we found that some requests (around 5 requests out of 500) got 502 error back.

and others are successfully reach PI through SOAP adapter.

Any idea?

[baskar_gopalakrishnan2 · Accepted solution]

>While doing performance testing for 500 requests, what we found that some requests (around 5 requests out of 500) got 502 error back.

Are you using load balancing dispatcher  or  any proxy server that delegate the request  to the web service not appropriately for some requests and this causing the problem? 502  error  sometime due to service temporarily overloaded too.

You might also want to check this link for reasons

http://www.checkupdown.com/status/E502.html

[YanGerzon]

Hi,

Has this been resolved?
If so, how?

Regards.

[iaki_vila]

Hi Chetan,

Like Raja says above, It's important to understand if the XML payload are different in the all messages that are you using for the performance test.

In the case that you are using a similar payload, the problem could be in several places:

A). You are using a proxy or a firewall that could not deal with that load of messages, and some of those are being rejected.

B) The web server is in a machine with a poor requeriments to support that load.

You should have in mind that is not problem of adapter PI or PI itself because a gateway problem normally happend before SAP PI, simply the communication socket can not be established between machines, the endpoint is not reacheable temporaly because the machine has not enough powerfull.

Regards.

[rajasekhar_reddy14]

Compare succesfull payload and failure payload messages and if you find any different then take action accordingly.