Hello Abhishek,
I'm an Architect on the Azure Service Bus Team.
I strongly recommend you use the Service Bus native Java client for this. The
client builds on Proton-J.
https://github.com/Azure/azure-service-bus-java
Batching isn't a standardized AMQP feature, and Service Bus uses a custom
A forward-slash '/' as the username and password separator is a surprise,
because [1] and more importantly [2]
Note: The rule in the quoted Proton-C doc formally disallows any occurrence of
'/' for the password, but it doesn't enforce it [3] so base64-encoded (with
'/') strings are factually
This may be my ignorance of JMS details, but why does a Qpid JMS consumer go
off and happily prefetch messages when its associated Session/Connection hasn't
even been start()'ed yet?
I just got misled by the trace output into believing that my app code's
receive/callback usage was wrong.
://azure.microsoft.com/en-us/blog/collaboration-and-federation-azure-service-bus-messaging-on-premises-futures/
Apache Qpid and Apache ActiveMQ Artemis are fine on-premises brokers to look at
and they speak the right protocol.
Best Regards
Clemens Vasters
Architect - Azure Messaging
@clemensv
Von: Suresh Gade
