Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.43.0
-
None
Description
When a receive with timeout call is made and the client configured to use zero prefetch, the client issues a credit, waits for a message to arrive, and if one doesn't in the given time it drains the credit to either get a message or ensure there is none available and remove the credit. If the message is already partially transferred (i.e it is multi-framed and so likely a larger message) at this point the client knows it doesn't need to drain, but the way it handles this triggers a later mishandling of completing the receive request when the message arrives.
Some related comments can be found here onwards.
Attachments
Issue Links
- is duplicated by
-
QPIDJMS-452 Receiving a large message with a jms polling consumer with timeout of 1 sec can hang when the timeout is reached while message is in transfer.
- Resolved