[INT-2833] Memory Leak in Aggregator Created: 26/Nov/12  Updated: 10/Jun/13  Resolved: 30/Nov/12

Status: Closed
Project: Spring Integration
Component/s: Core
Affects Version/s: 2.1.4
Fix Version/s: 2.2. GA, 2.1.5

Type: Bug Priority: Minor
Reporter: Gary Russell Assignee: Gary Russell
Resolution: Complete Votes: 0
Labels: PullRequest
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


Since 2.1, the aggregator maintains message group state in order to discard late-arriving messages.

However, forceComplete skips empty groups. This means, even if a MessageGroupStoreReaper is configured to expire groups, such groups are never expired (removed from the GroupMessageStore).

Empty groups should be considered eligible for reaping.

In 3.0, we might want to consider supporting 2 reaper cycles - reaping incomplete groups Vs. reaping empty groups.

Comment by Gary Russell [ 26/Nov/12 ]

PR: https://github.com/SpringSource/spring-integration/pull/683

Generated at Mon May 25 00:51:48 UTC 2020 using Jira 8.5.4#805004-sha1:0444eab799707f9ad7b248d69f858774aadfd250.