anonymous wrote : But, what about non_persistent messages ? In the current JM
implementation non_persistent delivery performance seems to be determined by the
relational database backend too as I wrote earlier, though it does not suffer from sync
writes as much as persistent delivery does.
The only time non persistent messages are written to the database is if paging kicks in.
Theres a configurable limit on a destination that controls how many messages can be held
in memory. at any point. Are you consuming the messages in your test?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128699#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...