This repository has been archived by the owner on Oct 12, 2023. It is now read-only.

Peak without lock max one message when entity partitioned #586

Open

MatthewDavidCampbell opened this issue Oct 11, 2018 · 0 comments

MatthewDavidCampbell commented Oct 11, 2018

Actual Behavior

Using 3.1.1 client
When using PeekBySequenceNumberAsync and messageCount > 1 the server should return more than one message if available
PeekBySequenceNumberAsync on non-partitioned entities respects the message count
From sequence number property is respected

Expected Behavior

PeekBySequenceNumberAsync on partitioned entities always returns only one message despite more on the node (both queue and deadletter, have not tested against subscription)

Versions

OS platform and version: Windows 10
.NET Version: 2.1 Core
NuGet package version or commit ID: 3.1.1

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.