Skip to content

Conversation

@mdumandag
Copy link
Contributor

We were using a new correlation id on invocation retries, which
can cause problems because the invocation is modified in-place.

We may have pending invocation entries with the key of correlation
id of X while the correlation id we would get from the client
message of the invocation is Y (Y > X).

It is changed so that the invocation is retried but now uses the
same correlation id.

We were using a new correlation id on invocation retries, which
can cause problems because the invocation is modified in-place.

We may have pending invocation entries with the key of correlation
id of X while the correlation id we would get from the client
message of the invocation is Y (Y > X).

It is changed so that the invocation is retried but now uses the
same correlation id.
@mdumandag mdumandag added this to the 4.0 milestone Dec 18, 2020
@mdumandag mdumandag self-assigned this Dec 18, 2020
@puzpuzpuz puzpuzpuz self-requested a review December 18, 2020 11:41
@mdumandag mdumandag merged commit 788c9c3 into hazelcast:master Dec 18, 2020
@mdumandag mdumandag deleted the use-same-id-on-retries branch December 18, 2020 12:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants