-
Notifications
You must be signed in to change notification settings - Fork 462
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncategorized exception occurred during JMS processing #967
Comments
Hi @bhautik-sakhiya , thanks for reaching out. |
@Netyyyy, thanks for reply. |
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. |
Seems like the same issue, let's wait for the server side fix |
Hi @bhautik-sakhiya , ServiceBus server side has a related fix recently for premium tier. |
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.
The text was updated successfully, but these errors were encountered: