IDACall transport error HTTP code 502

[dbscott525]

We’re using SmartGWT 5.0-p20150628

In automated tests we’re sporadically getting a 502 URL transport error for sc/IDACall.

This happens during an automated test where there are 100’s of interactions with our SmartGWT application so 1) we can predictably reproduce it, and 2) we can’t tell which specific interaction caused the error.

Where does this error come from?

Is there anything we can add to application to catch the error in our code rather than have it displayed in an alert?

[Isomorphic]

We can't comment on what might be causing the error - your server logs may indicate what went wrong.
As far as suppressing the alert when this occurs, you can use RPCManager.setHandleTransportErrorCallback() to set up custom handling for transport errors like this.

Regards
Isomorphic Software

[Isomorphic]

Note further than HTTP 502 (Bad Gateway) is not a status code that the IDACall Servlet ever returns. It's coming from some software earlier in the stack - for example, if you have an Apache web server using ajp relaying to a Tomcst Servlet engine, you will get 502 errors if the Tomcat server is down.