Unable to deliver message to service bus subscription about azservicebus HOT 18 OPEN

In Python I use to set the property "to" while sending message and on the Azure side I use to put filter on "to". How can I set the "to" property while sending the message to the topic?

There is a built-in method that allows you to set the to field for a message. https://docs.rs/azservicebus/latest/azservicebus/primitives/service_bus_message/struct.ServiceBusMessage.html#method.set_to

Something like this should work (not tested though)

let mut message = ServiceBusMessage::from("hello world");
message.set_to(String::from("<subscription name>"));
sender.send_message(message).await.unwrap();

from azservicebus.

I think all methods are documented on docs.rs (https://docs.rs/azservicebus/latest/azservicebus/index.html). The API mainly follows that of the dotnet SDK, so you could refer to the official tutorials written for the dotnet SDK and the look for the corresponding function in the rust SDK on docs.rs.

Just one more little help. How do I set content type of the message. Can you give an example?

This should do. https://docs.rs/azservicebus/latest/azservicebus/primitives/service_bus_message/struct.ServiceBusMessage.html#method.set_content_type

from azservicebus.

Is the below code snippet correct ?

let mut message = ServiceBusMessage::from("hello world"); message.set_to(String::from("")); message.set_content_type(String::from("application/json")); sender.send_message(message).await.unwrap();

Looks right to me. One more note, if you want an empty to field here, you could set it to None like

message.set_to(None);

That function takes anything that implements Into<Option<String>> and this includes String, Some(String) and None

from azservicebus.

I think all methods are documented on docs.rs (https://docs.rs/azservicebus/latest/azservicebus/index.html). The API mainly follows that of the dotnet SDK, so you could refer to the official tutorials written for the dotnet SDK and the look for the corresponding function in the rust SDK on docs.rs.

Just one more little help. How do I set content type of the message. Can you give an example?

This should do. https://docs.rs/azservicebus/latest/azservicebus/primitives/service_bus_message/struct.ServiceBusMessage.html#method.set_content_type

I will refer to this one. Thanks @minghuaw.

from azservicebus.

I tried many times but service bus subscription is not receiving message. My question is how a sender knows where to send the message (in which subscription of topic)
let mut sender = client
.create_sender(&topic_name, ServiceBusSenderOptions::default())
.await?;

from azservicebus.

This is not how the with_subscriber method should be used. That method is provided by the tracing crate for logging and the subscriber really means a log subscriber rather than your Service Bus subscription.

If you want to target a specific receiver, you should be using Service Bus Queue instead of Service Bus Topic as explained here (https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#topics-and-subscriptions).

A queue allows processing of a message by a single consumer. In contrast to queues, topics and subscriptions provide a one-to-many form of communication in a publish and subscribe pattern. It's useful for scaling to large numbers of recipients. Each published message is made available to each subscription registered with the topic. Publisher sends a message to a topic and one or more subscribers receive a copy of the message.

However, you could apply a filter on a subscription consumer, and you could modify certain properties of a message so that it can only pass through the filter of the desired consumer.

from azservicebus.

I will delete this issue once you consider it settled because you have pasted information (your connection string) that I consider confidential for you.

from azservicebus.

I will delete this issue once you consider it settled because you have pasted information (your connection string) that I consider confidential for you.

I used the dummy values.. :). Thanks.

from azservicebus.

This is not how the with_subscriber method should be used. That method is provided by the tracing crate for logging and the subscriber really means a log subscriber rather than your Service Bus subscription.

If you want to target a specific receiver, you should be using Service Bus Queue instead of Service Bus Topic as explained here (https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#topics-and-subscriptions).

A queue allows processing of a message by a single consumer. In contrast to queues, topics and subscriptions provide a one-to-many form of communication in a publish and subscribe pattern. It's useful for scaling to large numbers of recipients. Each published message is made available to each subscription registered with the topic. Publisher sends a message to a topic and one or more subscribers receive a copy of the message.

However, you could apply a filter on a subscription consumer, and you could modify certain properties of a message so that it can only pass through the filter of the desired consumer.

So I have a service bus "topic" under which I have "subscription". How do I send a message to that particular subscription?

from azservicebus.

Azure/azure-service-bus#366 . This diagram depicts the correct illustration.

from azservicebus.

So I have a service bus "topic" under which I have "subscription". How do I send a message to that particular subscription?

You send to the topic, and all subscriptions under that topic will get a copy of that message. You should use the topic name when you create the sender and use both the topic and subscription names when you create the receiver.

If you are looking for a one-to-one mapping, a queue is what you are after not topic

from azservicebus.

Azure/azure-service-bus#366 . This diagram depicts the correct illustration.

As shown in the diagram you quoted. You don't send to subscription directly. You send to the topic (by creating a sender to the topic), then all subscriptions under that topic will get the same message. Message filtering is handled on the subscription side, you could add filter rules on azure portal or in code following this example (https://github.com/minghuaw/azservicebus/blob/main/examples/manage_rules.rs)

from azservicebus.

The difference between queue, and topic/subscription is better explained here (https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-subscriptions)

from azservicebus.

Azure/azure-service-bus#366 . This diagram depicts the correct illustration.

As shown in the diagram you quoted. You don't send to subscription directly. You send to the topic (by creating a sender to the topic), then all subscriptions under that topic will get the same message. Message filtering is handled on the subscription side, you could add filter rules on azure portal or in code following this example (https://github.com/minghuaw/azservicebus/blob/main/examples/manage_rules.rs)

Thanks for the explanation. Yes I do have a filter on subscription to receive/filter message, but still not receiving message. Below are the system properties key in Azure to filter out the message: 1. correlationID 2.contenType 3. label/subject 4. messageId 5.replyto 6.replytoSessionId 7.sessionId 8. to

In Python I use to set the property "to" while sending message and on the Azure side I use to put filter on "to". How can I set the "to" property while sending the message to the topic?

from azservicebus.

In Python I use to set the property "to" while sending message and on the Azure side I use to put filter on "to". How can I set the "to" property while sending the message to the topic?

There is a built-in method that allows you to set the to field for a message. https://docs.rs/azservicebus/latest/azservicebus/primitives/service_bus_message/struct.ServiceBusMessage.html#method.set_to

Something like this should work (not tested though)

let mut message = ServiceBusMessage::from("hello world");
message.set_to(String::from("<subscription name>"));
sender.send_message(message).await.unwrap();

Thanks @minghuaw. This solved my problem. Also thanks for the prompt replies.

from azservicebus.

Just one more little help. How do I set content type of the message. Can you give an example?

from azservicebus.

Is the below code snippet correct ?

let mut message = ServiceBusMessage::from("hello world");
message.set_to(String::from(""));
message.set_content_type(String::from("application/json"));
sender.send_message(message).await.unwrap();

from azservicebus.

set_content_type

Got it thanks.

from azservicebus.