Jboss messaging with transactions and persistance optimizati

[damian.sinczak]

I would like to know if there is a possibility to force JBoss to persist messages sent to queue immediately. Currently in single transaction i send some about 600 000 messages (i can't change it because its my project nature) and I have great problem with RAM memory because queue during sending messages does not persist them but keep them in memory waiting for transaction commit. with the amount of messages I send JBoss takes all RAM available and i slows down a lot.

Is there a way to force JBoss messaging to save messages in database immediately and not keep them in memory waiting or commit. Of course I would like to have rollback functionality.

[gaohoward]

JBM 1.4 supports paging messages to DB to save memory. But it doesn't support large transactions so far.

[damian.sinczak]

Ok I understand that. But my another question is when I'm putting massages in smaller transactions (e.g. 50 000 at once) the problem is the same. JBoss messaging allocates memory and doesn't free it until last message is delivered to recipient. In other words when I put 600 000 messages in separate transactions (50 000 messages each) the problem is the same. Only solution would be committing next next transaction only when those committed in previous one were all delivered (which means that whole allocated memory was released).

[gaohoward]

You can configure the queue using proper fullSize parameter value to limit the memory usage in a queue. Please see the document for details.

[damian.sinczak]

that didn't help. I don't know how exactly persistence works for jboss messaging but allocated memory is kept until last message is delivered.

[gaohoward]

JBM treated transactional messages like this:

Each transaction has a in memory list to hold all its messages. When a transaction is being committed, it put those messages to the Queue for delivery. After the tx is committed, the associated list should be GCed.

The queue has paging functionality to prevent its memory from being used up. The fullSize is used to limit the num of messages that are hold in memory.

I think that will explain the situation you have.