AFAICT paging currently uses lastPageTransaction recorded in the journal to prevent pages
being processed more than once in case of failure.
This adds some complexity to paging.
JBM now contains automatic duplicate detection functionality which is enabled by just
adding a property MessageImpl.HDR_DUPLICATE_DETECTION_ID to the message.
Any messages with the same value will be rejected.
I am thinking that we can leverage this functionality in paging, which will allow us to
remove all the lastPageTransaction stuff and make the code simpler.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199065#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...