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?
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? 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 we are using persisted messages with durable subscriber messages should be delivered on any client or server failure (once they recover). Is that correct? Apologize for the layman questions but we are still in discovery mode as far as JBoss Messaging is concerned. Thanks for your help again. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3944291#3944291 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3944291 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
