Refactor Aggregator and Resequencer to better accommodate full span of use-cases [INT-2152]

[spring-operator]

Mark Fisher opened INT-2152 and commented

We should list the use-cases here, or point out which linked issue contains the test cases that provide those.

---

Sub-tasks:

• Time mismatches between Reaper being scheduled and timeout specified on the Reaper [INT-2013] #5998 Time mismatches between Reaper being scheduled and timeout specified on the Reaper

• Remove the role of the Sequence Size for the aggregators that are not relying on the default SequenceSizeReleaseStrategy [INT-2134] #6116 Remove the role of the Sequence Size for the aggregators that are not relying on the default SequenceSizeReleaseStrategy

• Resequencer should not be storing released messages. It should only remember the sequence number of the highest rated Message [INT-2135] #6060 Resequencer should not be storing released messages. It should only remember the sequence number of the highest rated Message

• Refactor GemfireMessageStore to rely on SimpleMessageGroup and remove KeyValueMessageGroup [INT-2142] #6124 Refactor GemfireMessageStore to rely on SimpleMessageGroup and remove KeyValueMessageGroup

• Consider refactoring the scope of synchronized blocks in AbstractCorrelatingMessageHandler [INT-2148] #6131 Consider refactoring the scope of synchronized blocks in AbstractCorrelatingMessageHandler

• Persist the state of the MessageGroups [INT-2155] #6140 Persist the state of the MessageGroups

• Expose 'expireGroupsUponCompletion' attribute on Aggregate [INT-2158] #6144 Expose 'expireGroupsUponCompletion' attribute on Aggregate

• Add support for specifying custom header for 'sequenceNumber' in Resequencer [INT-2159] #6145 Add support for specifying custom header for 'sequenceNumber' in Resequencer

• Set correlationId and sequenceNumber Headers in Messages Originated by Tcp Endpoints [INT-2162] #6148 Set correlationId and sequenceNumber Headers in Messages Originated by Tcp Endpoints

Issue Links:

• Implement Release Strategy for Unbounded Message Sequences in Resequencer [INT-1769] #5762 Implement Release Strategy for Unbounded Message Sequences in Resequencer

• Jdbc Message store accumulating messages in memory [INT-2151] #6134 Jdbc Message store accumulating messages in memory

• Consolidate GemfireMessageGroupStore to single region [INT-2064] #6053 Consolidate GemfireMessageGroupStore to single region
  ("supersedes")