"jaink" wrote:
Thanks for the suggestions. Couple of questions
1. JMSX properties seems to be optional. Can we assume that JMSXGroupid and JMSXGroupseq are supported by JBoss Messaging?
Support for these properties is mandatory - see JMS 1.1 spec 3.5.9
2. How do transactions work with "fullSize, pageSize and downCacheSize" parameters? If transactions require all messages (as part of the transaction) to be in memory at the same time how does the fullsize restriction work?
Once the transaction has been committed a subset of the messages can be in memory at once.
3. Not sure what is meant by "Since you won't be using transactions you will of course deal with the fact that your client or server could die after the set of messages was only partially sent."
If you split an image into 10 messages then send them one by, and the client crashes after sending the 5th message, then you have not sent all 10 messages so on recovery you need to deal with this and resend the other 5 otherwise you won't be able to re-assemble your large message on the receiving side.
if we are using persisted messages with durable subscriber messages should be delivered on any client or server failure (once they recover). Is that correct?
Yes, but that only applies to the ones you've actually sent. If you crash after number 5 then only 5 will be reliably delivered.
