[
https://issues.apache.org/jira/browse/CXF-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-6219.
------------------------------
Resolution: Won't Do
Fix Version/s: Invalid
More of a "cannot do". The way JAXB pulls base64 data from the parser means
that there is nothing we can do without support from the JAXB community or
similar to completely change how they do things. In some cases, that may even
involve a spec change to make byte[] be mapped to something else.
> Handling concurrent Base64 files causes memory overflow
> -------------------------------------------------------
>
> Key: CXF-6219
> URL: https://issues.apache.org/jira/browse/CXF-6219
> Project: CXF
> Issue Type: Improvement
> Components: Soap Binding, WS-* Components
> Affects Versions: 2.7.4
> Environment: Production
> Reporter: Abel Salgado Romero
> Labels: documentation
> Fix For: Invalid
>
>
> In a previous issue (https://issues.apache.org/jira/browse/CXF-5912) we were
> advised to update CXF version to avoid OOM errors.
> We did so (to 2.74) and the problem was fixed, we also applied a size limit
> of 20MB using the `org.apache.cxf.stax.maxTextLength` property.
> However, the memory consumption in the server is extremely higher than the
> actual data sent, having 1GB of Heap we get OOM sending just 6 concurrent
> requests of 20 MB.
> Reviewing some documents and other JIRA issues, we understand that Base64 is
> not optimized and not recomended. Can you confirm if this is the case or if
> there is a way to optimize how Base64 attachments are processed.
> Otoh, MTOM works like a charm ;)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
