Hi Hector, The apache commons http client isn't loaded by the appengine classloader now. It's included in a repackaged form for use in testing in appengine-api-stubs.jar, but shouldn't be included in the deployment. Any 3rd party library using that class will have the same problem.
You can replace it with javax.net.HttpURLConnection or the appengine's low level api URLFetchService. On Jun 6, 1:28 pm, "hector@ISB" <[email protected]> wrote: > My appspot (addama-systemsbiology.appspot.com) is getting lots of 500 > errors today. I haven't deployed any changes in a while. > > 2011-06-06 13:05:36.158 */addama/registry/mappings/tools/vera-sam-pipeline*500 > 11985ms 0cpu_ms 0kb Jakarta Commons-HttpClient/3.1,gzip(gfe) > 209.124.189.39 - - [06/Jun/2011:13:05:36 -0700] "POST > /addama/registry/mappings/tools/vera-sam-pipeline HTTP/1.1" 500 0 - "Jakarta > Commons-HttpClient/3.1,gzip(gfe)" "" ms=11986 cpu_ms=0 api_cpu_ms=0 > cpm_usd=0.000054 > *W *2011-06-06 13:05:36.158 > Request was aborted after waiting too long to attempt to service your > request. This may happen sporadically when the App Engine serving cluster is > under unexpectedly high or uneven load. If you see this message frequently, > please contact the App Engine team. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
