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

Timed out invocations without a response remain in memory forever #4113

Closed
mdogan opened this issue Nov 19, 2014 · 0 comments · Fixed by #4128
Closed

Timed out invocations without a response remain in memory forever #4113

mdogan opened this issue Nov 19, 2014 · 0 comments · Fixed by #4128
Assignees
Labels
Source: Internal PR or issue was opened by an employee Team: Core Type: Defect
Milestone

Comments

@mdogan
Copy link
Contributor

mdogan commented Nov 19, 2014

Invocations (and their operations) remain in invocations map forever (leak) if operation timeouts without a response (see OperationTimeoutException).

@mdogan mdogan added this to the 3.4 milestone Nov 19, 2014
@mdogan mdogan self-assigned this Nov 19, 2014
@mdogan mdogan modified the milestones: 3.3.4, 3.4 Nov 19, 2014
mdogan added a commit to mdogan/hazelcast that referenced this issue Nov 19, 2014
…hrown. Also async invocations should be notified about operation timeout. Fixes hazelcast#4113
mdogan added a commit to mdogan/hazelcast that referenced this issue Nov 19, 2014
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Jan 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Internal PR or issue was opened by an employee Team: Core Type: Defect
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants