@E_Sch any ideas? It seems like asynchttp_v1 may be failing on large responses. Here is a sample piston that compares large text and JSON responses:
In this configuration, the full text of Moby D fails to load with the same type of error (
DataCharacterLimitExceededException: Handler data length (526075) cannot be greater than 2500 characters.) but the JSON which is well over the 2500 limit works fine.
Sometimes the JSON errors out and sometimes it does not, so the data type is probably irrelevant. Seems like if
Piston waited at a semaphore for 9780ms is logged the piston has to schedule a wakeup in which case the response data, if too large, fails to process.