1.When we try to send a message to a queue or a topic using the following method,
com.azure.messaging.servicebus.ServiceBusSenderClient.sendMessage(ServiceBusMessage message)
it doesn't return MessageId of the message that just got pushed.
When a MessageId is not assigned in the ServiceBusMessage object, then a GUID gets created internally for that message to uniquely identify for duplicate detection. However this id is not propagated in the message or the response of the sendMessage()operation.
Expected Behavior
After successful execution of sendMessage operation, MessageId should be available as a response or in the ServiceBusMessage object. Having this information is critical in the real time distributed systems to uniquely identify each message that is being sent by this operation.
ServiceBusMessage object currently doesn't have any information after the send operation and getMessageId() method returns null but not the system generated GUID.
Versions
OS platform and version: Windows 10
Maven package version or commit ID: azure-messaging-servicebus » 7.4.1
Actual Behavior
1.When we try to send a message to a queue or a topic using the following method,
com.azure.messaging.servicebus.ServiceBusSenderClient.sendMessage(ServiceBusMessage message)
it doesn't return MessageId of the message that just got pushed.Expected Behavior
Versions