But the bottom line is, we have to start thinking like a user, and less like a developer. What is useful to a user? For large message functionality, people want to do just that - send large messages. This means messages up to many GB in size. These messages *cannot* fit in memory. The current implementation does not allow that. One way of fixing the current code is to provide input and outputstreams on the, (say), Message So.. when you receive your large message you initially just receive a message with just the headers, then you can extract the body using a stream api, which can be written to disk or whatever. Similarly when creating a message you can set another stream when sending the message, JBM will read from the stream for the body of the message. This needs to be available for JMS users too. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223495#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...