Details
Description
When a Spring Boot application with camel-undertow is deployed on a Kubernetes environment, say OpenShift, responses with large data may get truncated.
$ curl -sv hello-camel-tasato-test.7e14.starter-us-west-2.openshiftapps.com > out * Trying 52.36.115.21... * TCP_NODELAY set * Connected to hello-camel-tasato-test.7e14.starter-us-west-2.openshiftapps.com (52.36.115.21) port 80 (#0) > GET / HTTP/1.1 > Host: hello-camel-tasato-test.7e14.starter-us-west-2.openshiftapps.com > User-Agent: curl/7.64.1 > Accept: */* > < HTTP/1.1 200 OK < Accept: */* < User-Agent: curl/7.64.1 < Forwarded: for=27.95.227.48;host=hello-camel-tasato-test.7e14.starter-us-west-2.openshiftapps.com;proto=http;proto-version= < Date: Wed, 17 Apr 2019 11:18:54 GMT < X-Forwarded-Proto: http < X-Forwarded-Port: 80 < X-Forwarded-For: 27.95.227.48 < Content-Length: 1009999 < X-Forwarded-Host: hello-camel-tasato-test.7e14.starter-us-west-2.openshiftapps.com < Set-Cookie: a87d1be1aa3f6decad88f44c63db4670=7939401110c788ff04e98b94cb1b682f; path=/; HttpOnly < Cache-control: private < { [921 bytes data] * transfer closed with 698964 bytes remaining to read * Closing connection 0
Notice the curl message: transfer closed with 698964 bytes remaining to read
It depends on the throughput of the network and the size of response data.
Attachments
Issue Links
- links to