LTM iControlREST API request fails with HTTP 502 Bad Gateway

Also, if you are sending each REST call as an individual call there is a default limit of 10 HTTP connections to the platform. To adjust this you will need to navigate to system-->Preferences-->Advanced-->Maximum HTTP Connections To Configuration Utility. Not knowing your platform its hard to recommend a number to use, but this is potentially the cause of the 502 error.

UPDATE: we added 1055 iApps to our LTM (bringing the total to 3960) and consequently our script that uses REST to get the list of iApps is failing with the same Bad Gateway error. ONE time when trying the query with Postman this morning the actual Java timeout error made it back to me. It was this: https://{{F5-BIGIP-LTM}}/mgmt/tm/sys/application/service { "code": 400, "message": "Expiration was Wed Apr 15 09:06:18 EDT 2015", "restOperationId": 2760519, "errorStack": [ "java.util.concurrent.TimeoutException: Expiration was Wed Apr 15 09:06:18 EDT 2015", "at com.f5.rest.common.RestHelper$1.run(RestHelper.java:1825)", "at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)", "at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)", "at java.util.concurrent.FutureTask.run(FutureTask.java:166)", "at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)", "at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)", "at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)", "at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)", "at java.lang.Thread.run(Thread.java:722)\n" ] }