Comments (7)
Yello001
commented on May 27, 2024
#40457 seems to introduce the problem
undo changes #41826 fixed the issue
from azure-sdk-for-net.
jsquire
commented on May 27, 2024
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.
from azure-sdk-for-net.
github-actions
commented on May 27, 2024
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.
from azure-sdk-for-net.
JoshLove-msft
commented on May 27, 2024
The session processor will no longer drain as of #41834
from azure-sdk-for-net.
Yello001
commented on May 27, 2024
hello, yeah sure,
basically building up a Request/Response pattern over servicebus, with ServiceBusSender from ServiceBusClient.CreateSender and unique id to send
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
[Verbose] Azure-Messaging-ServiceBus: Creating a ServiceBusClient (Namespace: '<1>.servicebus.windows.net', Entity name: ''
[Verbose] Azure-Messaging-ServiceBus: A ServiceBusClient has been created (Identifier '<1>.servicebus.windows.net-<5>').
[Verbose] Azure-Messaging-ServiceBus: Creating a ServiceBusSender (Namespace: '<1>.servicebus.windows.net', Entity name: '<2>'
[Verbose] Azure-Messaging-ServiceBus: A ServiceBusSender has been created (Identifier '<2>-<identifier_link_1>').
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: StartProcessingAsync start.
[Verbose] Azure-Messaging-ServiceBus: Creating a ServiceBusSessionReceiver (Namespace: '<1>.servicebus.windows.net', Entity name: '<3>'
[Informational] Azure-Messaging-ServiceBus: Creating receive link for Identifier: <3>-<identifier_link_2>.
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: StartProcessingAsync done.
[Informational] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: SendAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: Creating send link for Identifier: <2>-<identifier_link_1>.
[Verbose] Azure-Messaging-ServiceBus: <3>-<identifier_link_2>: Requesting authorization to amqps://<1>.servicebus.windows.net/<3>
[Verbose] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: Requesting authorization to amqps://<1>.servicebus.windows.net/<2>
[Verbose] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: Authorization to amqps://<1>.servicebus.windows.net/<2> complete. Expiration time: 02/08/2024 09:04:11
[Verbose] Azure-Messaging-ServiceBus: <3>-<identifier_link_2>: Authorization to amqps://<1>.servicebus.windows.net/<3> complete. Expiration time: 02/08/2024 09:04:11
[Informational] Azure-Messaging-ServiceBus: Receive link created for Identifier: <3>-<identifier_link_2>. Session Id: <session_id>
[Verbose] Azure-Messaging-ServiceBus: A ServiceBusSessionReceiver has been created (Identifier '<3>-<identifier_link_2>').
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: Send link created for Identifier: <2>-<identifier_link_1>.
[Informational] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: SendAsync done.
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync done. Received '1' messages. LockTokens = <LockToken>00000000-0000-0000-0000-000000000000</LockToken>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: User message handler start: Message: SequenceNumber: 1138054, LockToken: 00000000-0000-0000-0000-000000000000
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: User message handler complete: Message: SequenceNumber: 1138054, LockToken: 00000000-0000-0000-0000-000000000000
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: SendAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: SendAsync done.
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync done. Received '1' messages. LockTokens = <LockToken>00000000-0000-0000-0000-000000000000</LockToken>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: User message handler start: Message: SequenceNumber: 1138055, LockToken: 00000000-0000-0000-0000-000000000000
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: User message handler complete: Message: SequenceNumber: 1138055, LockToken: 00000000-0000-0000-0000-000000000000
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: RenewSessionLockAsync start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: Creating management link for Identifier: <3>-<identifier_link_2>.
[Verbose] Azure-Messaging-ServiceBus: <3>-<identifier_link_2>: Requesting authorization to amqps://<1>.servicebus.windows.net/
[Verbose] Azure-Messaging-ServiceBus: <3>-<identifier_link_2>: Authorization to amqps://<1>.servicebus.windows.net/ complete. Expiration time: 02/08/2024 09:04:11
[Informational] Azure-Messaging-ServiceBus: Management link created for Identifier: <3>-<identifier_link_2>.
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: RenewSessionLockAsync done. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock complete. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: SendAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: SendAsync done.
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync done. Received '1' messages. LockTokens = <LockToken>00000000-0000-0000-0000-000000000000</LockToken>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: User message handler start: Message: SequenceNumber: 1138056, LockToken: 00000000-0000-0000-0000-000000000000
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: User message handler complete: Message: SequenceNumber: 1138056, LockToken: 00000000-0000-0000-0000-000000000000
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: SendAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: SendAsync done.
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync done. Received '1' messages. LockTokens = <LockToken>00000000-0000-0000-0000-000000000000</LockToken>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: User message handler start: Message: SequenceNumber: 1138057, LockToken: 00000000-0000-0000-0000-000000000000
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: User message handler complete: Message: SequenceNumber: 1138057, LockToken: 00000000-0000-0000-0000-000000000000
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: RenewSessionLockAsync start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: RenewSessionLockAsync done. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock complete. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync done. Received '0' messages. LockTokens =
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: RenewSessionLockAsync start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: RenewSessionLockAsync done. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock complete. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: RenewSessionLockAsync start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: RenewSessionLockAsync done. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock complete. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync done. Received '0' messages. LockTokens =
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: RenewSessionLockAsync start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: RenewSessionLockAsync done. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock complete. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync done. Received '0' messages. LockTokens =
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: RenewSessionLockAsync start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: RenewSessionLockAsync done. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock complete. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync done. Received '0' messages. LockTokens =
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: SendAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: SendAsync done.
[Informational] Azure-Messaging-ServiceBus: Management Link Closed. Identifier: <3>-<identifier_link_2>, linkException: .
[Informational] Azure-Messaging-ServiceBus: Receive Link Closed. Identifier: <3>-<identifier_link_2>, SessionId: <session_id>, linkException: .
[Warning] Azure-Messaging-ServiceBus: RunOperation encountered an exception and will retry. Exception: Azure.Messaging.ServiceBus.ServiceBusException: The operation did not complete within the allocated time 00:01:00 for object drain. (ServiceTimeout). For troubleshooting information, see https://aka.ms/azsdk/net/servicebus/exceptions/troubleshoot.
---> System.TimeoutException: The operation did not complete within the allocated time 00:01:00 for object drain.
at Microsoft.Azure.Amqp.ExceptionDispatcher.Throw(Exception exception)
at Microsoft.Azure.Amqp.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Azure.Amqp.ReceivingAmqpLink.DrainAsyncResult.End(IAsyncResult result)
at Microsoft.Azure.Amqp.ReceivingAmqpLink.<>c.<DrainAsyc>b__35_1(IAsyncResult r)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location ---
at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.ReceiveMessagesAsyncInternal(Int32 maxMessages, Nullable`1 maxWaitTime, TimeSpan timeout, CancellationToken cancellationToken) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Amqp\AmqpReceiver.cs:line 375
--- End of inner exception stack trace ---
at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.ReceiveMessagesAsyncInternal(Int32 maxMessages, Nullable`1 maxWaitTime, TimeSpan timeout, CancellationToken cancellationToken) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Amqp\AmqpReceiver.cs:line 403
at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.<>c.<<ReceiveMessagesAsync>b__44_0>d.MoveNext() in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Amqp\AmqpReceiver.cs:line 322
--- End of stack trace from previous location ---
at Azure.Messaging.ServiceBus.ServiceBusRetryPolicy.RunOperation[T1,TResult](Func`4 operation, T1 t1, TransportConnectionScope scope, CancellationToken cancellationToken, Boolean logTimeoutRetriesAsVerbose) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Primitives\ServiceBusRetryPolicy.cs:line 153
[Error] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync Exception: Azure.Messaging.ServiceBus.ServiceBusException: The session lock has expired on the MessageSession. Accept a new MessageSession. Tr
ackingId:<tracking_id>_G17_B33, SystemTracker:G17:119320424:amqps://<1>.servicebus.windows.net/-e517c57a;0:6:8:source(address:/<3>,filter:[com.microsoft:session-filter:<session_id>]), Timestamp:2024-02-08T08:39:46 (SessionLockLost). For troubleshooting information, see https://aka.ms/azsdk/net/servicebus/exceptions/troubleshoot.
at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.ThrowIfSessionLockLost() in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Amqp\AmqpReceiver.cs:line 1473
at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.ReceiveMessagesAsyncInternal(Int32 maxMessages, Nullable`1 maxWaitTime, TimeSpan timeout, CancellationToken cancellationToken) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Amqp\AmqpReceiver.cs:line 352
at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.<>c.<<ReceiveMessagesAsync>b__44_0>d.MoveNext() in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Amqp\AmqpReceiver.cs:line 322
--- End of stack trace from previous location ---
at Azure.Messaging.ServiceBus.ServiceBusRetryPolicy.RunOperation[T1,TResult](Func`4 operation, T1 t1, TransportConnectionScope scope, CancellationToken cancellationToken, Boolean logTimeoutRetriesAsVerbose) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Primitives\ServiceBusRetryPolicy.cs:line 153
at Azure.Messaging.ServiceBus.ServiceBusRetryPolicy.RunOperation[T1,TResult](Func`4 operation, T1 t1, TransportConnectionScope scope, CancellationToken cancellationToken, Boolean logTimeoutRetriesAsVerbose) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Primitives\ServiceBusRetryPolicy.cs:line 185
at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.ReceiveMessagesAsync(Int32 maxMessages, Nullable`1 maxWaitTime, CancellationToken cancellationToken) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Amqp\AmqpReceiver.cs:line 319
at Azure.Messaging.ServiceBus.ServiceBusReceiver.ReceiveMessagesAsync(Int32 maxMessages, Nullable`1 maxWaitTime, Boolean isProcessor, CancellationToken cancellationToken) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Receiver\ServiceBusReceiver.cs:line 330.
fail: RpcClient[0]
Error while processing Service Bus RPC response
Azure.Messaging.ServiceBus.ServiceBusException: The session lock has expired on the MessageSession. Accept a new MessageSession. TrackingId:<tracking_id>_G17_B33, SystemTracker:G17:119320424:amqps://<1>.servicebus.windows.net/-e517c57a;0:6:8:source(address:/<3>,filter:[com.microsoft:session-filter:<session_id>]), Timestamp:2024-02-08T08:39:46 (SessionLockLost). For troubleshooting information, see https://aka.ms/azsdk/net/servicebus/exceptions/troubleshoot.
at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.ThrowIfSessionLockLost() in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Amqp\AmqpReceiver.cs:line 1473
at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.ReceiveMessagesAsyncInternal(Int32 maxMessages, Nullable`1 maxWaitTime, TimeSpan timeout, CancellationToken cancellationToken) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Amqp\AmqpReceiver.cs:line 352
at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.<>c.<<ReceiveMessagesAsync>b__44_0>d.MoveNext() in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Amqp\AmqpReceiver.cs:line 322
--- End of stack trace from previous location ---
at Azure.Messaging.ServiceBus.ServiceBusRetryPolicy.RunOperation[T1,TResult](Func`4 operation, T1 t1, TransportConnectionScope scope, CancellationToken cancellationToken, Boolean logTimeoutRetriesAsVerbose) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Primitives\ServiceBusRetryPolicy.cs:line 153
at Azure.Messaging.ServiceBus.ServiceBusRetryPolicy.RunOperation[T1,TResult](Func`4 operation, T1 t1, TransportConnectionScope scope, CancellationToken cancellationToken, Boolean logTimeoutRetriesAsVerbose) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Primitives\ServiceBusRetryPolicy.cs:line 185
at Azure.Messaging.ServiceBus.Amqp.AmqpReceiver.ReceiveMessagesAsync(Int32 maxMessages, Nullable`1 maxWaitTime, CancellationToken cancellationToken) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Amqp\AmqpReceiver.cs:line 319
at Azure.Messaging.ServiceBus.ServiceBusReceiver.ReceiveMessagesAsync(Int32 maxMessages, Nullable`1 maxWaitTime, Boolean isProcessor, CancellationToken cancellationToken) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Receiver\ServiceBusReceiver.cs:line 330
at Azure.Messaging.ServiceBus.SessionReceiverManager.ReceiveAndProcessMessagesAsync(CancellationToken processorCancellationToken) in ...\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\src\Processor\SessionReceiverManager.cs:line 308
[Verbose] Azure-Messaging-ServiceBus: Closing a ServiceBusSessionReceiver (Identifier '<3>-<4>-S<session_id>').
[Verbose] Azure-Messaging-ServiceBus: A ServiceBusSessionReceiver has been closed (Identifier '<3>-<4>-S<session_id>').
[Verbose] Azure-Messaging-ServiceBus: Creating a ServiceBusSessionReceiver (Namespace: '<1>.servicebus.windows.net', Entity name: '<3>'
[Informational] Azure-Messaging-ServiceBus: Creating receive link for Identifier: <3>-<5>.
[Verbose] Azure-Messaging-ServiceBus: <3>-<5>: Requesting authorization to amqps://<1>.servicebus.windows.net/<3>
[Verbose] Azure-Messaging-ServiceBus: <3>-<5>: Authorization to amqps://<1>.servicebus.windows.net/<3> complete. Expiration time: 02/08/2024 09:04:11
[Informational] Azure-Messaging-ServiceBus: Receive link created for Identifier: <3>-<5>. Session Id: <session_id>
[Verbose] Azure-Messaging-ServiceBus: A ServiceBusSessionReceiver has been created (Identifier '<3>-<5>').
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: Processor RenewSessionLock start. SessionId = <session_id>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync done. Received '1' messages. LockTokens = <LockToken>00000000-0000-0000-0000-000000000000</LockToken>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: User message handler start: Message: SequenceNumber: 1138058, LockToken: 00000000-0000-0000-0000-000000000000
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: User message handler complete: Message: SequenceNumber: 1138058, LockToken: 00000000-0000-0000-0000-000000000000
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: SendAsync start. MessageCount = 1
[Informational] Azure-Messaging-ServiceBus: <2>-<identifier_link_1>: SendAsync done.
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync done. Received '1' messages. LockTokens = <LockToken>00000000-0000-0000-0000-000000000000</LockToken>
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: User message handler start: Message: SequenceNumber: 1138059, LockToken: 00000000-0000-0000-0000-000000000000
[Informational] Azure-Messaging-ServiceBus: <3>-<4>: User message handler complete: Message: SequenceNumber: 1138059, LockToken: 00000000-0000-0000-0000-000000000000
[Informational] Azure-Messaging-ServiceBus: <3>-<4>-S<session_id>: ReceiveBatchAsync start. MessageCount = 1
from azure-sdk-for-net.
Yello001
commented on May 27, 2024
Tested with #41834 from @JoshLove-msft
-> seems to solve the issue, no exception afterwards 👍
from azure-sdk-for-net.
jsquire
commented on May 27, 2024
Thanks, @Yello001. That removes the drain from this scenario, but the timeout is still unusual and I'd to understand the cause of that.
@JoshLove-msft: Do you think that the "success" here is the messages in prefetch being dispatched and then the attempt to acquire the session lock the next time around fails?
from azure-sdk-for-net.
Related Issues (20)
- [BUG] Recent commit introduced NullReferenceException in LogsQueryClient constructor HOT 6
- [BUG] SubscriptionResource.GetLocationsAsync fails with System.FormatException HOT 2
- [Schema Registry] Bump Apach.Avro dependency version
- What does MaxConcurrentCallsPerSession do? HOT 3
- Check and adjust timeouts for OpenAI HOT 1
- Validate MSAL MI API Integration (look for adoption blockers, breaking changes)
- STG 94 release prep
- Contradicting info with UploadAsync. HOT 1
- [QUERY] How to force to delete a CosmosDBSqlDatabaseResource? HOT 1
- [BUG] Azure.Provisioning KeyVault resource .. cannot set firewall rules. HOT 2
- Missing commas in the Communication Services Email SDK samples for .NET C# HOT 1
- Restore Key Vault Functionality Missing Azure SDK .NET C# HOT 2
- [BUG] TenantId may be empty string in Monitor GetActivityLogs response
- [BUG] ADLS SDK does not add Content-Length = 0 for flush requests explicitly HOT 2
- Move all provisioning libraries into respective service directories
- Decide whether to collapse Auth/ManagedIdentities into Azure.Provisioning
- [OpenAI] Update CodeGen to version 3.0.0-beta.20240329.2
- Any blocks not specified in the block list... HOT 1
- [FEATURE REQ] Support extensions in Postgres flexible HOT 1
- [FEATURE REQ] Add Method to Retrieve Analyzed Documents in DocumentIntelligence SDK HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from azure-sdk-for-net.