Azure Service bus Issue
Hello Team,
We are using azure service bus queue to read the real time messages with UMI to authenticate the connection from the Azure app services to Service bus queue.
Once in a week, we are getting some intermittent issue while making conenction to service bus from our applciations.
Please find the below error messages:
"az.sdk.message":"Freeing resources due to error.","connectionId":"MF_004841_1716617807816","entityPath":"crms.event.risktrigger","linkName":"crms.event.risktrigger_400259_1715779508493"}
az.sdk.message":"onLinkRemoteOpen","connectionId":"MF_bcb028_1715654618984","entityPath":"crms.event.risktrigger","linkName":"crms.event.risktrigger_5be376_1715121416625","action":"waitingForError"}
{"severityLevel":"Error","outerId":"0","message":"com.azure.core.amqp.exception.AmqpException: Connection reset, errorContext[NAMESPACE: crms01-p-servicebus.s
severityLevel":"Error","outerId":"0","message":"com.azure.core.amqp.exception.AmqpException: Connection reset, errorContext[NAMESPACE: crms01-p-servicebus.servicebus.windows.net. ERROR CONTEXT: N/A]","type":"reactor.core.Exceptions$ErrorCallbackNotImplemented","id":"0","rawStack":"reactor.core.Exceptions$ErrorCallbackNotImplemented: com.azure.core.amqp.exception.AmqpException: Connection reset, errorContext[NAMESPACE: crms01-p-servicebus.servicebus.windows.net. ERROR CONTEXT: N/A]\r\nCaused by: com.azure.core.amqp.exception.AmqpException: Connection reset, errorContext[NAMESPACE: crms01-p-servicebus.servicebus.windows.net. ERROR CONTEXT: N/A]\r\n\tat com.azure.core.amqp.implementation.ExceptionUtil.toException(ExceptionUtil.java:85)\r\n\tat com.azure.core.amqp.implementation.handler.ConnectionHandler.notifyErrorContext(ConnectionHandler.java:351)\r\n\tat com.azure.core.amqp.implementation.handler.ConnectionHandler.onTransportError(ConnectionHandler.java:253)\r\n\tat org.apache.qpid.proton.engine.BaseHandler.handle(BaseHandler.java:191)\r\n\tat org.apache.qpid.proton.engine.impl.EventImpl.dispatch(EventImpl.java:108)\r\n\tat org.apache.qpid.proton.reactor.impl.ReactorImpl.dispatch(ReactorImpl.java:324)\r\n\tat org.apache.qpid.proton.reactor.impl.ReactorImpl.process(ReactorImpl.java:291)\r\n\tat com.azure.core.amqp.implementation.ReactorExecutor.run(ReactorExecutor.java:91)\r\n\tat io.opentelemetry.javaagent.shaded.instrumentation.reactor.v3_1.ContextPropagationOperator$RunnableWrapper.run(ContextPropagationOperator.java:358)\r\n\tat reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:68)\r\n\tat reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:28)\r\n\tat java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)\r\n\tat java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)\r\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)\r\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)\r\n\tat java.base/java.lang.Thread.run(Thread.java:840)\r\n"}
itemType
exception
customDimensions
{"LoggerName":"reactor.core.publisher.Operators","Logger Message":"Operator called default onErrorDropped","SourceType":"Logger","ThreadName":"reactor-executor-1"}
client_Type
PC
client_IP
0.0.0.0
client_City
Amsterdam
client_StateOrProvince
Noord-Holland
client_CountryOrRegion
Netherlands
cloud_RoleName
crmscreditrisktriggeradministration
cloud_RoleInstance
d8bea6334829e0b367b158c67afdca25d2de29f30c494081296fd084ff232fcc
appId
04991c44-68b5-4c2a-851d-874e20c4af8f
appName
/subscriptions/995f9e3e-827e-47d5-ad7a-a82f14e5c212/resourcegroups/crms-p-rg/providers/microsoft.insights/components/crms01-p-ai
iKey
59107dab-6f3b-4379-8f8d-11a58ed863b2
sdkVersion
aw_java:3.5.1
itemId
44b25d64-146e-11ef-90ec-000d3a49baf6
itemCount
1
_ResourceId
/subscriptions/995f9e3e-827e-47d5-ad7a-a82f14e5c212/resourcegroups/crms-p-rg/providers/microsoft.insights/components/crms01-p-ai
Columns
Please let me know , if yopu need more infroamtion on this. This is the second request which I am raising for the same issue.
Please help us to resolve this intermittent issue ASAP, as we are in production already and facing this issue now and than.
Thank you!!