Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory Leak in Aggregator [INT-2833] #6807

Closed
spring-operator opened this issue Nov 26, 2012 · 1 comment
Closed

Memory Leak in Aggregator [INT-2833] #6807

spring-operator opened this issue Nov 26, 2012 · 1 comment

Comments

@spring-operator
Copy link
Contributor

Gary Russell opened INT-2833 and commented

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.


Affects: 2.1.4

Backported to: 2.1.5

@spring-operator
Copy link
Contributor Author

Gary Russell commented

PR: #683

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants