Spring/spring-integration
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

INT-3876: Track groups in correlation endpoints

Browse Source 
JIRA: https://jira.spring.io/browse/INT-3876

INT-3876 track groups ids in AbstractCorrelatingMessageHandler and docs

INT-3876 Fix merge conflict and add missing link in doc

INT-3876 Move groupId check in message group processor and rework on docs

INT-3876 Remove extra space from the doc

INT-3876 Fix checkstyle refer instance variable groupid correctly

INT-3876 Update aggregator doc with more details

* Polishing `aggregator.adoc`
* Rework `AbstractCorrelatingMessageHandlerTests.testDontReapMessageOfOtherHandler`
do not use redundant options
This commit is contained in:
Meherzad Lahewala
2017-11-20 14:50:39 -05:00
committed by Artem Bilan
parent f3072af192
commit 96aa7280a0
3 changed files with 45 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/reference/asciidoc/aggregator.adoc
View File

@@ -846,8 +846,8 @@ If the flag is set to true, then when the expiry callback is invoked, any unmark
[IMPORTANT]
=====
When using a `MessageGroupStoreReaper`, it is generally recommended to use a separate `MessageStore` for each correlating endpoint.
Otherwise, unexpected results may occur because one endpoint may remove another endpoint's groups.
When a shared `MessageStore` is used for different correlation endpoints, it is necessary to configure a proper `CorrelationStrategy` to ensure uniqueness for group ids.
Otherwise unexpected behavior may happen when one correlation endpoint may release or expire messages from others - messages with the same correlation key are stored in the same message group.
Some `MessageStore` implementations allow using the same physical resources, by partitioning the data; for example, the `JdbcMessageStore` has a `region` property; the `MongoDbMessageStore` has a `collectionName` property.