RE: HTTP responses time out

[Gustav Sinder]

Switched to Jetty instead of Restlet and it now works just fine.
Not sure what the difference in functionality is though..

Regards
/Gustav


-----Original Message-----
From: Gustav Sinder 
Sent: den 3 december 2014 10:05
To: users@camel.apache.org
Subject: RE: HTTP responses time out

Hi again,

We did some tcp dumps and found that Camel starts sending the payload back to 
the client.
It sends a few packets but then just stops without closing the connection 
leaving the client hanging.
Strange enough when looking at the Context in Hawtio, Camel considers the 
transaction to be completed..

/Gustav


-----Original Message-----
From: Gustav Sinder [mailto:gustav.sin...@ferrologic.se] 
Sent: den 28 november 2014 10:29
To: users@camel.apache.org
Subject: HTTP responses time out

Hi,

We've got an issue with some responses never being returned back to the HTTP 
client, making it time out.
It seems to depend on the length of the response returned from 
transformCanonicalToResponse().
A payload of ~10000 characters is returned ok but ~30000 characters are never 
returned.
It's reproducible every time and no errors are logged.

See route below, the log is written every time with the full correct payload.

Camel version 2.12

--------------------

<route id="InboundREST">
    <!-- RESTlet that receives XML files -->
    <from 
uri="restlet:http://localhost:{{listeningPort}}/{{listeningAdress}}?restletMethods=POST";
 />

    <!-- Validate the XML -->
    <to uri="validator:{{xsdLocation}}" />

    <!-- Transform XML to canonical -->
    <bean ref="transformToCanonical" method="transformRequestToCanonical" />

    <!-- Get data from backend -->
    <to uri="{{backend}}?timeout=300000" />

    <!-- Transform canonical to XML -->
    <bean ref="transformFromCanonical" method="transformCanonicalToResponse" />

    <convertBodyTo type="java.lang.String" />

    <to uri="log:foo?showAll=true&amp;maxChars=100000" /> </route>

--------------------

Thanks
/Gustav