I've been looking a bit at the jboss mq persistance code, and I have some questions. I'll state some of them from a user perspective, but my motivation is as a developer; that is, to address some of the 'problems' or 'limitations' these questions may uncover.
* Different DBMS system support: I realize the current schema is pretty simple, but nevertheless I think it's inevitible that you're going to want tweaks for different database servers, for performance reasons if nothing else. * Performance tuning/scalability: has any work been done to address potential bottlenecks for high message throughput, large numbers of queues or topics, etc.? * recovery robustness: recovery is a tricky thing since there's so many possible ways things can fail. What's been done to think about/test-for/defend-against all the possibilities? * two-phase commit: Is two-phase commit (XA) supported? I didn't see anything explicitly in the code, but pehaps I haven't yet read it carefully enough. * architecture: I haven't thought deeply about the trade-offs, but at first look it seems odd to create a transaction log table in a rdms, given that they can do the logging for you behind the scenes. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
