JS IAsyncEnumerable ConsumeAsync - high network traffic

[ealeykin]

Observed behavior

Not quite sure what is causing this, but this is what I observed after switching from IAsyncEnumerable to NextAsync for JS consumer:

IAsyncEnumerable ConsumeAsync was configured with MaxMsg = 1. Also MaxAckPending = 1.

Also many messages were NAKed without even being handled by application consumer handler (basically many messages were put to DLQ for no reason). Maybe related to Heart beat issue #793 .

Expected behavior

Network traffic is the same for both ConsumeAsync with MaxMsg=1 and NextAsync

Server and client version

server - 2.10
client - 2.5.12

Host environment

AWS/ECS

Steps to reproduce

NatsJSContext: ConsumeAsync vs NextAsync

[mtmk]

sorry for the late response. Just comparing the network for consume(maxMsgs=1) vs. next() and to me it looks like next is actually creating more traffic because it has the subscribe the unsubscribe to an inbox for every message, as expected. Could you provide more details about the calls with code samples? i will try to reproduce.