Open bhautik-sakhiya opened 5 months ago
Hi @bhautik-sakhiya , thanks for reaching out. Doesn't know how you use, but here is a sample may help you https://github.com/Azure-Samples/azure-spring-boot-samples/tree/main/servicebus/spring-cloud-azure-starter-servicebus-jms/servicebus-jms-topic
@Netyyyy, thanks for reply. I would like to add some additional information to get a better understanding. We have followed the jms in Spring to access Azure Service Bus. And, I believe Spring JMS is gonna take care of token generation.
Seems like the server will throw exception when the token is expired. One way to mitigate this issue is to connect via connection string, and we will check wether this is the behavior now of the Service Bus server side.
@saragluna, I appreciate your reply. Regrettably, there are no alternative choices available for us to establish a connection.
Hi @bhautik-sakhiya , ServiceBus server side has a related fix recently for premium tier.
So if you still meet this error in premium tier, please add environment property PN_TRACE_FRM=1
and provide the log info here, thanks.
The technologies we are currently using are:
We used JMS to handle message publishing(JMSTemplate) and listening(JMSListner) in the Azure ServiceBus Topic. JMS manages authorization and token generation, and we established the connection using namespace and used the clientId/secret to access servicebus.
Here we have to publish nearly millions of messages on the topic. Ultimately, The publishing process is too long. So in between we fetch the below-mentioned error. As a result, we may miss some messages in the topic.
After a few minutes, JMS will again generate the token for the provider, and message publishing will resume.