You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/04/18 02:41:00 UTC
[jira] [Work logged] (CAMEL-13428) camel-undertow - Response with
large data gets truncated on cloud
[ https://issues.apache.org/jira/browse/CAMEL-13428?focusedWorklogId=229548&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-229548 ]
ASF GitHub Bot logged work on CAMEL-13428:
------------------------------------------
Author: ASF GitHub Bot
Created on: 18/Apr/19 02:40
Start Date: 18/Apr/19 02:40
Worklog Time Spent: 10m
Work Description: tadayosi commented on pull request #2872: CAMEL-13428: camel-undertow - Response with large data gets truncated on cloud
URL: https://github.com/apache/camel/pull/2872
https://issues.apache.org/jira/browse/CAMEL-13428
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 229548)
Time Spent: 10m
Remaining Estimate: 0h
> camel-undertow - Response with large data gets truncated on cloud
> -----------------------------------------------------------------
>
> Key: CAMEL-13428
> URL: https://issues.apache.org/jira/browse/CAMEL-13428
> Project: Camel
> Issue Type: Bug
> Components: camel-undertow
> Affects Versions: 3.0.0-M2
> Environment: On Kubernetes / OpenShift
> Reporter: Tadayoshi Sato
> Assignee: Tadayoshi Sato
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When a Spring Boot application with camel-undertow is deployed on a Kubernetes environment, say OpenShift, responses with large data may get truncated.
> {code}
> $ 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
> {code}
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)