1

I have to store the request xml in to database. I was using header variable to do that.

exchange.getIn().setHeader("inputRequestXml", body);

it was working for some files And I was getting below exception for some files, it seems like because of the file size.

 413 Request entity too large

So I have changed the implementation by using camel property, like below

exchange.setProperty("inputRequestXml", body);

Now I am not getting the exception. But I am afraid that will it handle the bigger files in actual PROD environment. So i want to know, What would be the size limit of header variable and property?

Hari
  • 97
  • 1
  • 14

2 Answers2

5

Exchange properties have no limit, its just a HashMap that stores key/values in the memory of the JVM.

Message headers is also just a HashMap, but headers are part of the message contract, and depending on which Camel components (transports) you use then these headers may be in use, eg HTTP headers, SOAP headers, JMS headers etc. And when so you may have header limitations that are caused by these transports.

You can find more details and it can be a good idea to read the free chapter 1 of the Camel in Action 2nd edition book which explains the important Camel concepts.

Claus Ibsen
  • 56,060
  • 7
  • 50
  • 65
4

Apache Camel has no limit on Headers and Properties. It is limited by Java heap size, as every other object.

Error you have posted is HTTP error, you are probably sending it over HTTP and remote server returned this error. Apache Camel translates Message#headers as HTTP headers and you have exceeded size limit configured on server.

See: Maximum on http header values?

Switching to Properties worked, because Properties are not tranferred over HTTP. You might be interested in endpoint options copyHeaders=false and headerFilterStrategy

Bedla
  • 4,789
  • 2
  • 13
  • 27