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

The public service consumer must remain connected if network connection lost #240

Closed
aregtech opened this issue Aug 27, 2023 · 0 comments · Fixed by #246
Closed

The public service consumer must remain connected if network connection lost #240

aregtech opened this issue Aug 27, 2023 · 0 comments · Fixed by #246
Assignees

Comments

@aregtech
Copy link
Owner

Description:
Observed that if a Service Provider (Stub) has connected Consumers (Proxies), which one is running on local process and the other is on remote, and if connection is lost, then Service Consumer, which is running on the same process, may also stop receiving messages.

This should be investigated, observed and tested well. Probably with additional example with simple features.

In addition, check that Service Provider removes all notification subscription of the disconnected Service Consumer, so that:

  • On the disconnect all requests, notifications and responses are cleaned, because makes no sense to process;
  • On the re-connect can restart everything to pass the current state of data;
  • If a request is pending, it should be canceled.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Reviewed
Development

Successfully merging a pull request may close this issue.

1 participant