Implement "blanket" rollback for failed filter or multi-cache entryprocessor invocation

[GoogleCodeExporter]

An EntryProcessor invocation may affect keys not known beforehand, and may 
partially succeed leaving uncomitted entries. This can happen for:
* filter based invocation
* keyset invocation of an EntryProcessor that affects several caches through 
partition-local operations via backing maps i.e. implements MultiCacheProcessor

The failure will set rollback only mode, but we must ensure that the rollback 
is a blanket rollback across the affected caches - all entries of that 
transaction id.

Original issue reported on code.google.com by whitmars...@gmail.com on 17 May 2012 at 12:44

[GoogleCodeExporter]

Original comment by whitmars...@gmail.com on 17 May 2012 at 12:45

• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

In fact, the whole "blanket rollback" concept is unneccessary - complete 
implementation of the affected partitions concept, and simply mark all 
partitions as affected if an exception is encountered - also relevant for issue 
19

Original comment by whitmars...@gmail.com on 6 Jun 2012 at 2:59

• Changed state: Started

[GoogleCodeExporter]

Original comment by whitmars...@gmail.com on 11 Jun 2012 at 9:38

• Changed state: Verified