System.ArgumentException in CosmosJsonDotNetSerializer

[ViconiaDeVier]

Describe the bug
After upgrading Microsoft.Azure.Cosmos library from 3.23.0-preview to 3.28.0-preview and Microsoft.Azure.Cosmos.Encryption.Custom library from 1.0.0-preview02 to 1.0.0-preview03 we started to see a lot of System.ArgumentException on our PROD env:
unhandled exception System.ArgumentException: Stream was not readable.
at System.IO.StreamReader..ctor(Stream stream, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean leaveOpen)
at Microsoft.Azure.Cosmos.Encryption.Custom.CosmosJsonDotNetSerializer.FromStream(Stream stream)
at Microsoft.Azure.Cosmos.Encryption.Custom.EncryptionFeedIterator.ConvertResponseToDecryptableItems(Stream content)
at await Microsoft.Azure.Cosmos.Encryption.Custom.EncryptionFeedIterator.ReadNextWithoutDecryptionAsync(?)
at await Microsoft.Azure.Cosmos.Encryption.Custom.EncryptionFeedIterator`1.ReadNextAsync(?)

I see that there was something similar fixed in this PR so I was wondering if it's possible that there can be similar issue related to CosmosJsonDotNetSerializer ?
It doesn't seem that it is happening because of some problem with particular items since they were read and decrypted successfully during another attempts.
So it looks that sometimes for some reason the stream is closed before the item was decrypted

Actual behavior
Stream is closed before item is decrypted

Environment summary
SDK Version: 3.28.0-preview
OS Version (e.g. Windows, Linux, MacOSX) Windows

---

Upd:
Some additional details which might help investigation.
This issue normally appears in East Japan. At one moment of time we see this error happens on different instances, processing one particular partition at one moment of time (but it's different partitions over the time). Also - that happens only for the cases when we connect to East Japan account as a read replica account.

[kr-santosh]

ResponseMessage responseMessage = await this.feedIterator.ReadNextAsync(cancellationToken);
seems to return a closed stream. Need the Cosmos Core team to have a look at this. @sourabh1007

[kr-santosh]

Hi @sboshra can the query team have a look at this issue.

[kirankumarkolli]

Is the account strong/bounded-staleness?

[ViconiaDeVier]

@kirankumarkolli the account is bounded-staleness

[kirankumarkolli]

Related fix is released in 3.29-preview (discussed offline)