-
Notifications
You must be signed in to change notification settings - Fork 58
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
[v1.1.1] Handle Lost Invocations [API-992] #684
Conversation
@@ -47,6 +50,42 @@ func TestListenersAfterClientDisconnected(t *testing.T) { | |||
}) | |||
} | |||
|
|||
func TestNotReceivedInvocation(t *testing.T) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want to avoid accessing internals and do a test from public API, you can send a long running task to the remote. An EntryProcessor for example which just sleeps. And then close the member.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder whether there is an entry processor you mentioned exists in the test jar. I'll try to find that.
Can we rename GroupID to ConnectionID ? We don't have a concept like group in other clients. |
GroupLost
event which contains the connection ID (group ID). and the reason of disconnection. Invocation service subscribes to that event, and closes matching invocations. TheConnectionClosed
event is not used for this purpose in order to avoid depending oninternal/cluster
for theinternal/invocation
package which would result in cyclic dependency.