In what area(s)?

/area runtime

What version of Dapr?

1.1.x

Expected Behavior

When using a pub-sub component connected to an azure servicebus topic/subscription with sessions enabled, messages with the same Session ID are sent to the client application in the same order that they are produced.

Actual Behavior

When using a pub-sub component connected to an azure servicebus topic/subscription with sessions enabled, messages with the same Session ID are being sent to the client app in parallel.

Steps to Reproduce the Problem

1 - Create a topic and subscription in an azure servicebus namespace with ordering/sessions enabled
2 - Produce 2 different messages with the same session id to the topic
3 - Create a pub-sub component connected to the same servicebus namespace
4 - In a sample application, subscribe to the topic/subscription via the pub-sub component in step 3, specifying the "requireSessions" metadata as "true".

This repository exposes the issue, but you will need your own azure servicebus namespace:
https://github.com/Bloop-Tech/dapr_servicebus_session_concurrency_example

Release Note

RELEASE NOTE: