Short answer: Action results (eg. Blob/Clob values) are internally serialized by the framework, which might consume some memory. I'm not aware that we have a solution for your use-case yet.
I don't have any good ideas yet, how to solve this. On 2019/10/24 17:56:04, Brian K <harvestmoon...@gmail.com> wrote: > Hi, > > Using version 1.17.0, I noticed that if I return a large Blob from my > domain service, it can cause issues. My specific case was a 600 MB PDF > that caused an OutOfMemoryException when returning to the browser. Is > there a facility to stream a large file response back to the browser? > > Sorry I don't have a stack trace available right now, but I recall that the > error happened after the Blob was created in my domain service. I think I > saw JAXB serialization in the stack trace. > > Thanks! > Brian >
