Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.2.4
-
None
-
None
-
None
Description
A client connected to a queue on a broker via a tcp: transport connection receives no indication of a broker restart.
This leaves the client waiting forever for messages on the queue but the broker does not have a subscription for that client. The client has no indication that it must initiate a reconnection with the broker.
Attachments
Issue Links
- relates to
-
AMQCPP-316 Unable to receive any messages after re-starting message broker
- Resolved