Project: mule
Issue MULE-8307: HTTP requester throws timeout errors with POST request
Appears to be related to the "Expect: 100 continue" header with Grizzly, that is found in HTTP/1.1 POST request. The bug reproduces in ESB 3.6 and 3.6.1, also GW 1.4. attached is the jmx file, using this proxy app for ESB (no Gateway tags). https://github.com/mulesoft/performanceworks/blob/master/APPS/PROXY-MCD/100B/http_module_proxy/proxy.xml If you change the method to GET instead of POST, you will not get the error. You should be able reproduce it easily. Wai ERROR 2015-02-11 00:29:48,112 [[PabloTestAPI_NewHTTP].proxyConfig.worker.09] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : Error sending HTTP request. Message payload is of type: BufferInputStream Code : MULE_ERROR-29999 -------------------------------------------------------------------------------- Exception stack is: 1. null (java.util.concurrent.TimeoutException) org.glassfish.grizzly.impl.SafeFutureImpl$Sync:357 (null) 2. Error sending HTTP request. Message payload is of type: BufferInputStream (org.mule.api.MessagingException) org.mule.module.http.internal.request.DefaultHttpRequester:190 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MessagingException.html) -------------------------------------------------------------------------------- Root Exception stack trace: java.util.concurrent.TimeoutException at org.glassfish.grizzly.impl.SafeFutureImpl$Sync.innerGet(SafeFutureImpl.java:357) at org.glassfish.grizzly.impl.SafeFutureImpl.get(SafeFutureImpl.java:264) at com.ning.http.client.providers.grizzly.GrizzlyResponseFuture.get(GrizzlyResponseFuture.java:173) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ********************************************************************************
Story points: 13