Pub/Sub component with Session enabled Azure Service Bus Topics doesn't complete messages in sequence

[yogeshgotam]

Expected Behavior

Azure service bus with sessions not only guarantees queuing & extraction order of messages but also the processing order of messages.
With sessions enabled pub/sub component should ensure that subscriber completes processing of messages in the order they were received.

Say, there are 2 messages in the queue for same session and 1 subscriber.

1. The subscriber receives message1.
2. The subscriber completes processing message1, which takes roughly 60 seconds.
3. The subscriber receives message2.
4. The subscriber completes processing message2, which takes about 10 seconds.

Actual Behavior

1. The subscriber receives message1.
2. The subscriber receives message2, while it is still not done with processing message1.
3. The subscriber completes processing message2, which took about 10 seconds.
4. The subscriber completes processing message1, which took about 60 seconds.

Steps to Reproduce the Problem

• Create sample publisher & subscriber applications using Dapr.Client v1.15.2 & Dapr.AspNetCore v1.15.2
• Configure pubsub component
  
• Set subscription metadata with the following properties.
  requireSessions: true
sessionIdleTimeoutInSec: 120
maxConcurrentSessions: 4
• Setup event handlers in subscriber such that it takes ~60s to process message1 & ~10s to process message2.
• Publish message1 with SessionId=test1.
• Publish message2 with SessionId=test1.

Release Note

RELEASE NOTE:

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[yogeshgotam]

Can you please keep this active? Thanks.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[yogeshgotam]

Please keep this active

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[yogeshgotam]

Keep this active, please.