[BUG] Drain excess credits when using sessions to ensure FIFO (#40457) - Timeout and Session Lock Expiration #41827
Assignees
Labels
Client
This issue points to a problem in the data-plane of the library.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
needs-team-attention
Workflow: This issue needs attention from Azure service team or SDK team
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Service Bus
Comments
github-actions
bot
added
Client
|
Hi @Yello001. Thank you for reaching out and we regret that you're experiencing difficulties. The timeouts that you're experiencing are not something that we're able to reproduce in our test suite nor that other developers have reported. Could you help us better understand your scenario? It would be helpful to see how you're creating and configuring the processor and to understand how sessions are used for messages. We would appreciate if you could capture a 5-minute slice of Azure SDK logs around the timeout behavior, so that we can understand what the clients are seeing. Any other context that would help us reproduce what you're seeing would also be greatly appreciated. |
jsquire
added
needs-author-feedback
|
Hi @Yello001. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue. |
|
The session processor will no longer drain as of #41834 |
|
hello, yeah sure, new ServiceBusMessage(messagePayload) { ReplyToSessionId = _sessionId }and ServiceBusClient.CreateSessionProcessor with this options to receive var options = new ServiceBusSessionProcessorOptions
{
PrefetchCount = 2,
ReceiveMode = ServiceBusReceiveMode.ReceiveAndDelete
};
options.SessionIds.Add(_sessionId);first messeges get response as expected, and after a couple minutes the processing blocks and throws exception afterwards. the logs from start till exception |
github-actions
bot
added
needs-team-attention
|
Tested with #41834 from @JoshLove-msft |
|
Thanks, @Yello001. That removes the drain from this scenario, but the timeout is still unusual and I'd to understand the cause of that. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Library name and version
Azure.Messaging.ServiceBus 7.17.1, 7.17.2
Describe the bug
#40457 seems to run into a timeout when calling
and subsequent in ServiceBusSessionProcessor.ProcessErrorAsync handler:
Expected behavior
In Azure.Messaging.ServiceBus 7.17.0 without the
DrainAsycthere's no exceptionActual behavior
causing:
and subsequent in ServiceBusSessionProcessor.ProcessErrorAsync handler:
Reproduction Steps
using the CreateSessionProcessor and ProcessMessageAsync of ServiceBusClient
Environment
.Net Core 8.0, Windows 11
The text was updated successfully, but these errors were encountered: