Listening to multiple subscriptions in different azure service bus namespaces

85 views
Skip to first unread message

Haripraghash Subramaniam

unread,
Nov 2, 2016, 3:02:22 PM11/2/16
to Particular Software
Helpful information to include
Product name: Nservicebus 6, Nservice bus azure transport 7
Version:
Stacktrace:
Description:

Hi,

I have a nservicebus based endpoint which is hosted on azure as a worker role. We use ASB as the transport and this is a receiveonly endpoint. We are trying to see if there is a option to listen to an event that can be sent from two different namespaces. For reasons of High Availability, the event publisher will publish events in ASB namespace1  and in ASB namespace 2. The receiver needs to listen to both the ASB subscriptions. Is this possible to achieve with INamespacePartitioningStrategy ?

Sean Feldman

unread,
Nov 4, 2016, 12:59:31 AM11/4/16
to Particular Software
You're are correct.
The simplest way in this case would be to use RoundRobinNamespacePartitioning strategy provided OOTB.

Haripraghash Subramaniam

unread,
Nov 4, 2016, 1:29:31 AM11/4/16
to Particular Software
Ok. These strategies sound like they work on Partitioned queues and topics. If the topics are not partioned then these sytartegies dont work? Is there a way to subscribe to say a primary namespace and a secondary namespace at the same time and keep listening to them both?

Sean Feldman

unread,
Nov 4, 2016, 1:26:40 PM11/4/16
to Particular Software
This is what topology strategies should do OOTB.
Thank you for raising an issue. We'll have a hotfix and that should let you achieve what you need.
Please keep tracking GitHub issue for status updates.

Haripraghash Subramaniam

unread,
Nov 8, 2016, 4:45:10 PM11/8/16
to Particular Software
Thank you for that. Is this being scheduled for near future? with near future meaning next 1-2 sprints?

Sean Feldman

unread,
Nov 8, 2016, 8:35:01 PM11/8/16
to Particular Software
This is scheduled for the next patch release, 7.0.3. It will be announce here the moment patch is available on NuGet.
If you'd like to track closely the progress, please keep tracking GitHub issue for status updates as it will indicate all the status updates.

Sean Feldman

unread,
Nov 24, 2016, 6:42:43 PM11/24/16
to Particular Software
Reply all
Reply to author
Forward
0 new messages