This content has been marked as final.
Show 1 reply
-
1. Re: General Architecture Question: Slow/Failed consumers disrupting JMS messaging
clebert.suconic Mar 9, 2012 5:26 PM (in response to bnc119)Paging was meant for scenarios like these.
Anyway.. as a general advice.. I always recommend batching consuming when possible.
Consumer 1000 messages, insert 1000 records, single commit (XA if possible) in both places.
JMS2 will introduce batch consumers because of that, and hopefully it will eventually make to EE.