RobertIndie opened a new issue, #166:
URL: https://github.com/apache/pulsar-dotpulsar/issues/166
### Description
If the consumer is disconnected due to a network issue, the consumer may
hang up when reconnecting to the broker. The consumer cannot turn back to the
`Active` state and cannot receive any messages even though the network is back.
### Reproduction Steps
- Start the consumer. The consumer changed to `Active` state
- Disconnect the computer network. For instance, let the broker run in
another machine and then disconnect the local machine's wifi.
- Wait for about 3-5 minutes. The consumer would be changed to `Disconnect`
state during this period.
- Reconnect the network
- The consumer cannot change to `Active` state. Cannot receive any messages
### Expected behavior
The consumer is able to reconnect and receive messages after the network
issue is fixed.
### Actual behavior
The consumer cannot change to `Active` state. Cannot receive any messages
### Regression?
I don't think so. It could be reproduced in v1.0.2 and the latest master
version.
### Known Workarounds
_No response_
### Configuration
- .Net version: .Net 6.0
- OS: macOS, win
- Architecture: x86
### Other information
_No response_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
