Caused by: com.azure.core.amqp.exception.AmqpException: org.apache.qpid.proton.engine.TransportException: connection aborted, errorContext[NAMESPACE: . ERROR CONTEXT: N/A]

Abhishek Yadav 0 Reputation points
2024-01-02T13:15:44.52+00:00

Hi,

I think we are able to connect our azurebus but it seems like connection getting dropped.

Could you please check the below logs and try to help us.

Caused by: com.azure.core.amqp.exception.AmqpException: org.apache.qpid.proton.engine.TransportException: connection aborted, errorContext[NAMESPACE: #######. ERROR CONTEXT: N/A]
	at com.azure.core.amqp.implementation.ExceptionUtil.toException(ExceptionUtil.java:85) ~[azure-core-amqp-2.8.8.jar!/:2.8.8]
	at com.azure.core.amqp.implementation.handler.ConnectionHandler.notifyErrorContext(ConnectionHandler.java:351) ~[azure-core-amqp-2.8.8.jar!/:2.8.8]
	at com.azure.core.amqp.implementation.handler.ConnectionHandler.onTransportError(ConnectionHandler.java:253) ~[azure-core-amqp-2.8.8.jar!/:2.8.8]
	at org.apache.qpid.proton.engine.BaseHandler.handle(BaseHandler.java:191) ~[proton-j-0.33.8.jar!/:na]
	at org.apache.qpid.proton.engine.impl.EventImpl.dispatch(EventImpl.java:108) ~[proton-j-0.33.8.jar!/:na]
	at org.apache.qpid.proton.reactor.impl.ReactorImpl.dispatch(ReactorImpl.java:324) ~[proton-j-0.33.8.jar!/:na]
	at org.apache.qpid.proton.reactor.impl.ReactorImpl.process(ReactorImpl.java:291) ~[proton-j-0.33.8.jar!/:na]
	at com.azure.core.amqp.implementation.ReactorExecutor.run(ReactorExecutor.java:91) ~[azure-core-amqp-2.8.8.jar!/:2.8.8]
	... 7 common frames omitted
Azure Service Bus
Azure Service Bus
An Azure service that provides cloud messaging as a service and hybrid integration.
700 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. MayankBargali-MSFT 70,936 Reputation points Moderator
    2024-01-03T12:01:09.48+00:00

    @Abhishek Yadav Thanks for reaching out. As per the error it indicates that that there was an error with the AMQP connection to Azure Service Bus. Specifically, the error message indicates that the connection was aborted due to a transport error.

    This could be caused by a number of issues, such as network connectivity problems, incorrect connection string or authentication issues.

    To troubleshoot this issue, you can try the following steps:

    1. Check your network connectivity to Azure Service Bus. Ensure that your firewall settings are not blocking the connection and validate if your service bus is not enabled for the virtual network. If yes, then the connection is allowed from your client IP address or is in the same virtual network as service bus.
    2. Verify that the connection string you are using is correct. You can find the connection string in the Azure portal under the Service Bus namespace.
    3. Check that the authentication credentials you are using are correct. Ensure that the SAS key and SAS key name are correct.

    If you are still having issues this would need to be looked into one-on-one support to validate the details.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.