Re: Empty/null response from netty4-http template producer

2018-03-28 Thread Alex Soto
Created issue : https://issues.apache.org/jira/browse/CAMEL-12414 Best regards, Alex soto > On Mar 28, 2018, at 12:46 PM, Alex Soto wrote: > > Anybody has any insight on what may be happening? Should I submit a Jira

Re: Empty/null response from netty4-http template producer

2018-03-28 Thread Alex Soto
Anybody has any insight on what may be happening? Should I submit a Jira ticket? Best regards, Alex soto > On Mar 27, 2018, at 3:18 AM, Owain McGuire > wrote: > > Alex, > > Just had a quick look. > > The post in the Rest DSL route goes to

Re: Empty/null response from netty4-http template producer

2018-03-27 Thread Alex Soto
Owain, Thank you for taking a look. You are right, I made a mistake while preparing this stripped down project. The truth is that the Rest DSL is actually not needed to reproduce this particular issue, so I have now removed the Rest DSL and kept only a single route consuming from Netty-HTTP

Re: Empty/null response from netty4-http template producer

2018-03-27 Thread Owain McGuire
Alex, Just had a quick look. The post in the Rest DSL route goes to direct:echo-route but your echo-route does not have a "from direct:echo-route". My understanding is that the REST DSL generates a route that will have already consumed the POST and then once it has sent the exchange to the

Re: Empty/null response from netty4-http template producer

2018-03-26 Thread Alex Soto
Hello, I have put a simple project that demonstrates this problem. This does not appear to be related to stream caching, as I have enable stream caching in both Camel contexts. https://github.com/lexsoto/camel-karaf-netty-producer-test/tree/master

Empty/null response from netty4-http template producer

2018-02-22 Thread Alex Soto
Hello, I am having some problems migrating to Camel 2.20.2 from 2.17.4.This has been working before, but now the response is null. I have access to the server logs and everything there looks good, i.e., the server is sending a response, but client is unable to get it. Here is the client