Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
When a durable client with registered interests, connects to the server:
1. it sends a readyForEvent message to the queue, the sever enqueues a marker message.
2. then the server enqueues all the puts messages to the queue.
3. the client disconnects (either by connection failure or by re-auth failure)
4. the client reconnects back to another server, the other server makes its queue primary, and enqueues another marker message.
5. if the first marker message hasn't been delivered to the client yet, the queue manager will delete the first marker message since marker messages should be conflated. Then all puts messages will be delivered before the marker message, thus the client won't put the values in its client cache.
Attachments
Issue Links
- links to