I had problems with OutOfMemory as well and the settings for Queues that receive
potentially huge messages I use are
<attribute name="FullSize">20</attribute>
| <attribute name="PageSize">5</attribute>
| <attribute name="DownCacheSize">5</attribute>
This works but you have to be aware of that a QueueBrowser will only list messages that
are in memory.
I would be great if there was an option to hold just the message header (the
JMS-properties) in memory if the payload exceeds a configurable size.
This way "small" messages would still be in memory and performance would be
good. The payload for bigger messages would be loaded from the database when needed
keeping memory usage low.
What do you think?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140357#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...