-
Notifications
You must be signed in to change notification settings - Fork 26.5k
Closed
Labels
component/need-triageNeed maintainers to triageNeed maintainers to triagetype/need-triageNeed maintainers to triageNeed maintainers to triage
Description
Pre-check
- I am sure that all the content I provide is in English.
Search before asking
- I had searched in the issues and found no similar issues.
Apache Dubbo Component
Java SDK (apache/dubbo)
Dubbo Version
Dubbo Java 3.2.12, OpenJDK 17.0.11, MacOS 14.4.1 / Centos 7.9
Steps to reproduce this issue
- Refer to the document (dubbo triple stream) to implement triple stream provider and consumer
- Start the provider first and then the consumer. Both the provider and the consumer can receive and send messages normally.
- Restart the provider, and the consumer calls onNext to send a message without any error, but in fact the provider does not receive the corresponding message, and the consumer also does not receive the provider message
What you expected to happen
When the provider is restarted, the consumer is disconnected from the provider, the channel becomes inactive, and then there is no callback notification (grpc stream will trigger the onError method) to allow the consumer to reconnect manually, and there is no automatic reconnection.
Anything else
No response
Are you willing to submit a pull request to fix on your own?
- Yes I am willing to submit a pull request on my own!
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
component/need-triageNeed maintainers to triageNeed maintainers to triagetype/need-triageNeed maintainers to triageNeed maintainers to triage
Type
Projects
Status
Todo