So you think sending the file in full size is not performance efficient? I wonder what happens when the receiving app get the file, will the full content of the file load into memory or will just part of it will get loaded and the rest will load on demand?
Thanks, Can you chunk the file? In this case you might split it between multiple producers and consumers and play with the number of producers/consumers and chunck size. You may send and process chuncks concurrently and also limit the message size. Just one option... -- View this message in context: http://old.nabble.com/best-approach-to-transfer-large-File%2C-modify-content-on-receive-tp27766358p27766785.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
