Good evening Claus,
Thank you for your swift reply.
In fact, I have omitted to say that I already turned on the stream caching
(my fault, I work hard 7/7, please forgine me), by doing this:
getContext().setTracing(true);
getContext().setStreamCaching(true);
getContext().getStreamCachingStrategy().setSpoolDirectory("./");
getContext().getStreamCachingStrategy().setSpoolThreshold(64 *
1024);
getContext().getStreamCachingStrategy().setBufferSize(130 *
1024);
Following what I read from Netty4-HTTP component documentation.
Before setting this during my test sessions, I had same result (body null),
but no response header as well.
And to be honest, I have also omitted that I set netty configuration like
this:
NettyHttpConfiguration configuration = super.getConfiguration();
//configuration.setAllowDefaultCodec(true); Not supported by
Netty
configuration.setAllowSerializedHeaders(false);
configuration.setConnectTimeout(CONNECT_TIMEOUT_IN_SECONDS);
configuration.setAutoAppendDelimiter(false);
configuration.setBroadcast(false);
configuration.setClientMode(true);
configuration.setDisconnectOnNoReply(true);
configuration.setKeepAlive(false);
configuration.setLazyChannelCreation(false);
configuration.setReconnect(false);
configuration.setSync(true);
configuration.setTcpNoDelay(true);
configuration.setSend503whenSuspended(true);
configuration.setThrowExceptionOnFailure(true);
configuration.setTransferException(false);
And I have created a JNDI Registry in camel context (I don't think it has an
impact, but).
This time, I promise there is no more hidden information!
By the way, I don't know if it can have an incidence, but the ECB server
returns a xml file (application/xml), but the content-type indicated is
"text".
Thanks again for your reply.
Kind regards,
Stéphane Coutant
--
View this message in context:
http://camel.465427.n5.nabble.com/Netty-Http4-client-Null-body-whereas-content-length-0-tp5793490p5793494.html
Sent from the Camel - Users mailing list archive at Nabble.com.
