logo
down
shadow

Azure Service Bus AMQP Exception


Azure Service Bus AMQP Exception

By : user2949188
Date : November 16 2020, 06:23 AM
fixed the issue. Will look into that further RE: 1. ACS or SAS
Yes, you can use SAS with AMQP. Policy name instead of username, and URL encoded key instead password. The URL encoding is required to handle any non-alphanumeric characters in key value as +, /, or =.
code :
amqps://<policyname>:<urlencoded(key)>@<namespace>.servicebus.windows.net


Share : facebook icon twitter icon
How to use AMQP 1.0 with the Service Bus .NET API (Azure)

How to use AMQP 1.0 with the Service Bus .NET API (Azure)


By : Damian Chodorek
Date : March 29 2020, 07:55 AM
should help you out After opening the ports 5671, 5672, 5760, 5761, 5762, 9350, 9354 on my windows firewall did not help and after disabling the windows firewall completely for debugging did not work, I just tried it with a mobile as a hotspot to work around the company network and now it is working with just adding 'TransportType=Amqp' at the end of the connection string. Modifying default ports is not necessary. I have to talk with the IT guys now... :)
So, if you get the message "No connection could be made because the target machine actively refused it" or in German "Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte" check your firewall...
code :
ServiceBusEnvironment.SystemConnectivity.Mode = ConnectivityMode.Http;
Azure Servicebus AMQP URL not accepted / or how to connect Liberty to Azure Service Bus

Azure Servicebus AMQP URL not accepted / or how to connect Liberty to Azure Service Bus


By : Jimmy.Que
Date : March 29 2020, 07:55 AM
With these it helps The answer is that I use a JCA adapter which is not able to connect to a AMQP 1.0 broker. In the example application I use qpid amqp 1.0 client jms. At the moment there is no amqp 1.0 JCA resource adapter. Also there is no further work on the resource adapter: Qpid Jira Ticket 7716
Azure Service bus with AMQP - how to specify the session ID

Azure Service bus with AMQP - how to specify the session ID


By : vmor
Date : March 29 2020, 07:55 AM
I think the issue was by ths following , The SessionId property is mapped to AMQP message properties.group-id. The Qpid JMS client should map it to JMSXGroupID property, so try the following, createBytesMessage.setStringProperty("JMSXGroupID", "session-1");
Getting "amqp:internal-error" when peeking messages from Azure Service Bus Queue using AMQP, rhea and Node

Getting "amqp:internal-error" when peeking messages from Azure Service Bus Queue using AMQP, rhea and Node


By : Angelina Webb
Date : March 29 2020, 07:55 AM
hope this fix your issue With help of Azure Service Bus team, I was able to find a solution to this problem (in fact, they gave me this solution). Essentially elements of messageBody should be properly encoded using AMQP types.
Following code works:
code :
  var messageBody = {
    'from-sequence-number': client.types.wrap_long(1),
    'message-count': client.types.wrap_int(5)
  };

  const msg = {
    application_properties: {
      operation: 'com.microsoft:peek-message'
    },
    body: messageBody,
    reply_to: 'receiver-link'
  };
Azure Service Bus : Amqp Idle Timeout condition = amqp:link:detach-forced

Azure Service Bus : Amqp Idle Timeout condition = amqp:link:detach-forced


By : Süleyman KANDİLCİ
Date : September 23 2020, 08:00 PM
I hope this helps . The exception is indicating that Azure has closed the producer because it was idle for to long, meaning it hadn't sent a message within the timeout (some documentation here). You might be able to work around this when using the CachingConnectionFactory by configuring the cache producers option to false so that producers are created on demand but I'm not entirely sure on that as I don't have any way to test it.
This isn't a Qpid JMS client level bug but rather the behaviour of Azure kicking in where after I think it's ten minutes of no activity on a link it will forcibly close the link. In a non-spring based application you'd have to account for this by catching the JMSException on send either attempting to create a new producer and sending again or by tearing down the whole connection and starting over. Your reaction somewhat depends on foreknowledge that you are using Azure and knowing that this can happen.
shadow
Privacy Policy - Terms - Contact Us © ourworld-yourmove.org