Yes if you can see file content is actually loaded in
populateRequestParameters(), I think it's likely to be a bug. Please make sure
it's not just a file name, and update the description with what you found. If
you can attach a minimal reproducer project that would be better.
On 10/20/2016 07:
I can add a description that parameter is read twice.
2016-10-20 13:34 GMT+03:00 Vova Shelgunov :
> *Tomohisa*, actually initially I posted a bug in Jira (
> https://issues.apache.org/jira/browse/CAMEL-10399), but Claus closed it,
> can I reopen it?
>
> 2016-10-20 10:49 GMT+03:00 Tomohisa Igarash
*Tomohisa*, actually initially I posted a bug in Jira (
https://issues.apache.org/jira/browse/CAMEL-10399), but Claus closed it,
can I reopen it?
2016-10-20 10:49 GMT+03:00 Tomohisa Igarashi :
> Hmm that smells like a bug in DefaultHttpBinding.populateRequestParameters(),
> it shouldn't read a pa
Hmm that smells like a bug in DefaultHttpBinding.populateRequestParameters(),
it shouldn't read a parameter value which is already handled in
populateAttachments(). Would you file a JIRA for it?
On 10/20/2016 03:18 PM, Vova Shelgunov wrote:
Hi,
I tried to debug populateRequestParameters in De
Hi,
I tried to debug populateRequestParameters in DefaultHttpBinding and
noticed that request parameters contain file (with byte[] array value) that
I am sending to endpoint:
It is a reason why I have OOM error.
Let me note that I am sending file using google http client:
I attached Multi
Hi,
It seems like the OOM occurs when it's mapping request parameters, but not
request body which is passed as an InputStream by default. Do you have any
large parameter other than body?
Note that if you enable allowJavaSerializedObject, then body is deseriallized
as a Java Object, may cause O
Hi Andrea,
Yes, I run application using jar file. Java has 1G heap.
Actually I assumed that camel will not read file in single string, but will
use InputStream to read the data.
2016-10-19 15:28 GMT+03:00 Andrea Cosentino :
> Is the camel-context deployed as a simple JAR? What are you using ins
Is the camel-context deployed as a simple JAR? What are you using inside the
Debian container? How much memory has your container?
Did you set JVM_OPTS witch specific values for max Heap size and min Heap size?
--
Andrea Cosentino
--
Apache Camel PMC Member
Apach
Hi,
I catched this OutOfMemoryError when I sent a 250 MB file to jetty endpoint:
java.lang.OutOfMemoryError: Java heap space
at java.lang.StringCoding.decode(StringCoding.java:215)
at java.lang.String.(String.java:463)
at java.lang.String.(String.java:515)
at
org.eclipse.
