If you can put the binary part of your message as a attachment, it can dramatically reduce the memory usage.
That said, avoid using base64 binary encoding as much as possible should be able to improve the performance. In Fuse ESB, you should pass through the attachment just as "attachment", but not need change to base64 and pass through it. Both Camel Message and NMR message support to propagate attachment, so inside FUSE ESB, pass through an attachment means pass through a stream handler and unless you send attachment over transport protocol, you needn't read the attachment content.
yes Freeman, I know, ussage of the message attachmet ist the best, better than to use binary attributes.
But I can not change the webservice definition.
Can I do some another memory optimization on FuseESB?
Can message comprimation feature of cxf bus help me?